Default upsert behavior violated

[DnOberon]

Bug Description

I have an object that is sent over and over into DeepLynx. The central node is the LoadWorkflow (L) in the middle. It attaches to an existing change object (C) and is decomposed by its steps V, M, and P.

The process updates properties on steps, V, M, and P, but just sends the entire combined step subgraph in over and over through the process. The type mapping defines node creation on L, V, M, and P (with the unique ID dropdown value set) and edge creation between L and everything else. I have confirmed that the IDs for all these object aren't changing in the payload, however, the, L, V, M, and P objects are being recreated over and over with each payload.

Steps to Reproduce

See container 63 on DeepLynx azureacc, and the type mapping created Mon, 24 Jun 2024 16:20:47 GMT

Impact

Creates a logically compromised graph that breaks the business logic for the Windchill doc automation.