0
Not a bug

Connection-aware join not persisting for outgoing link when join criteria field value changes - new adapter entity is created and old one is left behind

Adrian Corston 1 year ago in UNIFYBroker/Plus updated by Beau Harrison (Senior Software Engineer) 1 year ago 6

When a locker's Cloud Group Name field is updated this configuration causes the creation of a new adapter/connector entity.  The old adapter/connector entity is retained.  After the 

The functionality is needed to allow solutions to have changes to entity key/join fields flow through to downstream systems.

-1

When I tested the connection-aware join strategy previously I believe it's likely that I didn't identify this behaviour because (a) Outgoing Deprovisioning was set to True and (b) the consequential deprovision and reprovision of the adapter entity was indistinguishable from an update operation (specifically, the entity ID was retained).

Under review

Hi Adrian

How reproducible is this issue for you? I was unable to do so. Also, an adapter entity's entity id is not retained if it is deprovisioned so it sounds like it was working correctly in your previous testing.

Hi Beau, it's reproducible in the Metlifecare DEV environment on the link/adapter/locker shown.  I can demonstrate it if required.

Can you reproduce and take note of the id of the existing entity and compare that with which of the post sync duplicate entities contains the updated values? Is a new entity being created for the update or is the old one being updated?

Can you also try turning off outgoing provisioning for that link temporarily and see if there is a difference?

I can't replicate this, please close the ticket.