- UNIFYBroker Forum
- UNIFYBroker/Plus
-
Questions
UNIFYBroker/Plus attempting to join source to incorrect target
Log says:
20221129,21:30:25,UNIFYBroker,Link,Error,"Request to sync changes on link failed. Request to sync changes on link Employee > AD User (ad53013b-b271-4ed6-a959-dc11aeaa5eca) in direction outgoing failed with message Source entity '0b5d5a72-fd60-4777-b1ef-f1d4a035c87d' cannot be joined to ambiguous join targets: [391e6395-a3c2-424c-9799-30a98508ac1f, 5a6e4486-75f8-4487-ab8f-4eeccf06a524]. Cannot proceed with join. [Count:4321]. Duration: 00:00:04.5645340
Link join criteria is:
Source entity is:
Target entities are:
Why would an attempt to join to 5a6e4486-75f8-4487-ab8f-4eeccf06a524 be happening, given it doesn't match the join criteria?
Answer
There is a possibly-related but less critical issue with a duplicate ambiguous join target getting reported twice on the incoming direction. In this case the error is legitimate, because there are two entities with the same join criteria field value, but the error itself is showing the same target entity (7a252472-3043-4018-b122-f16033b18a65) twice for some reason:
20221129,21:30:21,UNIFYBroker,Link,Error,"Request to sync changes on link failed. Request to sync changes on link Employee > AD User (ad53013b-b271-4ed6-a959-dc11aeaa5eca) in direction incoming failed with message Source entity '391e6395-a3c2-424c-9799-30a98508ac1f' cannot be joined to ambiguous join targets: [0b5d5a72-fd60-4777-b1ef-f1d4a035c87d, 7a252472-3043-4018-b122-f16033b18a65, 7a252472-3043-4018-b122-f16033b18a65]. Cannot proceed with join. [Count:2309]. Duration: 00:00:07.1606939
Hi Adrian,
Are there any joins that exist against the source entity currently? ( 0b5d5a72-fd60-4777-b1ef-f1d4a035c87d ) Or is it a newly provisioned entity?
Under Remove Joins for the link I can see that entity already showing, which I believe means it is already joined. I don't know how to see which locker it's joined to.
The root cause of this was staff from the customer's outsourced IT department updating employeeID values wrongly, in contravention of documented processes.
Please close this ticket and mark 'not a bug'.
Customer support service by UserEcho
The root cause of this was staff from the customer's outsourced IT department updating employeeID values wrongly, in contravention of documented processes.
Please close this ticket and mark 'not a bug'.