UNIFYConnect instance created some new users in an AD connector, but then the next time it ran the following error appeared:

When a lower priority incoming adapter source field value change is processed by a Changes Polling operation, higher priority field values from the target locker are not written back to the adapter entity.  When a Baseline Sync operation runs they are.  The practical outcome of this is that UNIFYBroker only enforces managed field values in downstream systems when a Baseline Sync is run.

Here's an example from a UNIFYConnect instance: MemberDNs is a multi-valued string field for managing group membership.

Incoming from Azure Cloud Groups:

Outgoing to AD Groups:

The mapping priorities in the Locker are as follows (i.e. Azure Cloud Groups is set as a higher priority mapping than AD Groups):

When the MemberDNs field of the Azure Cloud Groups entity changes (i.e. add or remove a value) that change goes through to the AD group and the AD group's membership is updated with the current values from the Azure Cloud Group and locker entity, as expected.

However, if the group membership's membership is then changed directly in AD that change then comes back as far as the adapter entity, but doesn't flow into the locker entity (and neither should it, because there are already a higher priority values mapped into the locker from the Azure Cloud Group adapter).  However, the correct values from the locker are not being written back to the adapter, which is the functionality we would like to have, so that when a change is made to a managed attribute in a downstream system UNIFYBroker/Plus will quickly revert that change and enforce the correct upstream value.

When a subsequent Baseline Sync is run on the AD Groups link the correct value from the locker is written to the adapter and the downstream system is updated to enforce the value.  This is a functional workaround, but scheduling frequent Baseline Sync operations has an operational overhead.

It's ~9:30am and I just added and enabled an Import All and Import Changes schedule to a connector.  The Import All I set to run at 12:55:57am, and the Import Changes every 1 minute.  The following appeared, which doesn't look right - 1am isn't an hour away, and one minute is not 10 hours away:

On the Remove Joins screen the Created and Modified dates are both set to "00001-01-01 00:00:00Z" for Adapter entities:

This is not impacting me in any way and I'm just mentioning it for completeness.

The following UI error appears whenever I attempt to view joins via the 'Remove Joins' menu option on a Link in the Netwealth UNIFYConnect DEV instance:

I am using Chrome on the jumpbox VM, logged in with my UNIFY credentials. The error is not written to the UNIFYBroker log.

UNIFYBroker/Plus would be easier to operate if the following logging and UI messages were added or made more clear:

* A log summary of the count of entities provisioned and deprovisioned by a locker synchronisation (this may already be there, but the terminology is "added" rather than "provisioned" - it would be nice if this was consistent with the UI and clearly delineated as being different to entities "added" to the adapter via reflection)

* An log explanation of the reason(s) why an entity's provision was Incomplete - i.e. which required fields are missing, or whatever else it was that caused it to be Incomplete.

* A way to identify all of the logging messages that are part of the same synchronization operation.  In a busy log file it's hard to see the wood for the trees...

* Not to report un-joined and un-provisioned entities for a linker as Incomplete during Baseline Synchronization.  The configuration clearly doesn't want these entities in the locker - but the yellow (i) box that appears seems to suggests that something may have gone wrong with them.

A Locker field value change is not appeared in an Adapter when Changes Synchronization runs.  The same Locker/Adapter are able to provision objects just fine.

The UNIFYBroker/Plus config and logs are available in the Netwealth UNIFYConnect DEV instance; the Locker is "Employee", the Adapter is "SPOL Employee Suspensions", the Link is "Employees > SPOL Employee Suspensions".  To trigger the change I make a change to a field value in the Employee connector source (an SFTP CSV file), run an Import All on the "ELMO Employees" connector, a Changes Synchronization on the "ELMO Employees > Employees" Link, then finally the Changes Synchronization on the "Employees > SPOL Suspended Employees" Link (which causes the following error to be written to the log):

The follow error occurs:

To replicate, create a Link for an Adapter, delete the Adapter and then attempt to edit the Link.

After deleting a Link, Adapter and Connector the following error is persistently appearing in the Netwealth UNIFYConnect DEV instance:

Could you please investigate and advise how to get rid of it?

All my UNIFYConnect adapters are showing the following error in the log, and all the Pending Changes are stuck in the adapter:

This is happening on the Netwealth UNIFYConnect instance.

Could you please investigate and fix or let me know what I've done wrong?