Duplicate locker entities are provisioned when the incoming link join criteria includes fields not in the connector's key and only non-key field value are changing
Adrian Corston 2 years ago in UNIFYBroker/Plus • updated by Beau Harrison (Senior Product Software Engineer) 2 years ago • 2
For an adapter entity already joined to a locker entity, if any of the join field values change but the entity ID remains unchanged (i.e. none of the underlying connector's keys change) then the previously joined locker entity is retained and a new one is provisioned instead (or presumably joined, if there was a matching entity already present in the locker).
This bug was previously reported in https://voice.unifysolutions.net/en/communities/6/topics/4209-locker-entity-not-deprovisioned-when-adapter-entity-join-field-values-change# but that ticket covers a number of different bugs experienced and so this simple ticket is being created for improved clarity.
Customer support service by UserEcho
Beau's patch for #4209 with "Connection-aware" selected for the new "Join Strategy" setting addresses this issue.