- UNIFYBroker Forum
- UNIFYBroker/Plus
-
Questions
Duplicated join target for NULL field value where there is no target with that field value
I am seeing: Baseline synchronization failed with the message "Source entity 'b5d56da5-a8af-4088-b98c-4b78a693b093' shares a join target with another source entity: 'fa457ecd-b5a7-4708-886b-747ca82da40a'. Cannot proceed with join.". See logs for more details.
Both source entity have a join field value of NULL, and there are no target entities with a join field value of NULL.
I tried deleting entities and reloading them, but the error remains. The mapping of field values through to other locker entities is not happening, and I would like to know if the join failure is the cause of this.
Answer
Hi Adrian
As the error message says, both of those source entities have the same join target, which may or may not exist until provisioning occurs. If the schema fields you're using can contain nulls and you want the sync to progress I'd recommend adding a Has Value filter on the join fields.
Hi Beau. Incoming provision is False so why would it be trying to provision locker entities?
It's not provisioning anything, that comes at a latter stage. Join target resolution happens before that and needs the source entities being synchronized to be in a valid state for it to succeed.
The adapter entities don't have corresponding locker entities, and incoming provisioning isn't enabled so a join makes no sense. I am confused why this configuration results in errors?
Would these failures be the cause of other entity field values not mapping, which is the main question I'm looking for an answer to?
Beau's advice above implies a rule that un-inbound-filtered join target field values must always be unique or else Baseline Sync will fail and no mappings will be applied, even if incoming provisioning is False and the target entities will never exist.
Customer support service by UserEcho
Hi Adrian
As the error message says, both of those source entities have the same join target, which may or may not exist until provisioning occurs. If the schema fields you're using can contain nulls and you want the sync to progress I'd recommend adding a Has Value filter on the join fields.