Broker Plus Incompletes in sync from adapter to locker

Hi Daniel,

An incomplete sync is when either one of the fields configured in a join rule is null, or if the synced entity is missing a value that is marked as required in the target schema.

I'll add this information to the synchronization documentation.

The join rule is on employeeID so I don't think that's the problem because it's populated for all users. This is during an initial data load and the aim is just to get all the Active Directory users into the locker before initiating syncs from Aurion. What I'm trying to do is similar to projection in MIM. I don't really know what the target schema would be in this case

The target schema is the schema for the target entity context. The target entity context is where the entity will be synchronized to. For an incoming sync, that would be the locker, For an outgoing sync, the adapter.

So if the target schema is the locker, there doesn't seem to be a required fields in a locker. So the join attribute is populated and there are no required fields so what could the problem be?

Actually, there's two objects where the joining attribute, employeeID, is null. This wouldn't prevent all of them though would it?

Have you tried increasing the logger verbosity? Missing joins should be logged.

If you want to attach your extensibility configuration I'll take a look.

Yes the locker is empty. The link should provision to AD ordrinarily but the intent was to import the AD entities into the locker first so that when the Aurion feed is brought in, only accounts that haven't joined to an AD account are created.

Created documentation for Synchronization Status. Should make things clearer for the future.

The problem is getting initial load working. I can't bring the ad side in first and that means when i enable the ad side it'll create all the aurion accounts rather than join and only create the ones that haven't joined. What is the approach here for broker plus?