Version 9.1.140 (3 February 2025)

Problem

Solution

Problem

When only a Value Object has changed on an Entity (as opposed to a normal property) the auditing does not pick up that the entity should be audited because it does not evaluate the Value Object properties of the Entity.

Solution

Unfortunately, there is no easy way to directly check the previous vs current values of Value Object properties as you would with a normal entity property change. Value Objects are immutable; any 'change' deletes the previous entity reference and adds a new one.
To still be able to pick up changes, however, you can access all the 'Added' reference entities of an entity (the value objects essentially) and then compare that to the list of deleted entities from the Change Tracking.
If it is the same type and has the same FK then assume that this Deleted entity is the pre-change version of the Added entity.
Once the deleted entity is retrieved compare Added against Deleted properties and return true if any changes.

Problem

The org nodes are duplicated when no org structure exists and multiple users are linked to the node
When importing nodes with accents in the name the import fails
The bulk import to V8 for the job structure is blocked by the full org structure import when errors occur

Solution

Remove unused caching check between node creation and replace with existence check on the newly created nodes
Add accent escapes when querying the existing org nodes.
Reorder the bulk import types
Correct 1000 appointment recursion error

Problem

Solution