![](/s/cache/7d/53/7d53b04c16d6ef66897d1a534be84eba.png)
Duplicate changes registered for the same entity in the adapter
Priority: Low/Medium
Impact: Higher than necessary UNIFYConnect resource consumption
With a connector and adapter configured in UNIFYBroker, and the adapter has multiple transformations registered (such as joins and future dated changes), a change appears to be registered in the change table for each combination of entity + transformation.
This can result in 8-10 changes being registered for the same entity. While this isn't impactful from a change perspective (the latter computations of changes result in no actual changes being made to the adapter entity), a connector import of 7000 entities is resulting in upwards of 60,000 changes being registered which results in unnecessary delays of processing and computation on the database.
Answer
![](/s/cache/21/92/2192bdaa5cc1ed11af11f2653ef995b5.png)
I also have another small DEV UNIFYConnect environment with currently 17 records in my users connector and when I make a (minor) change to one record in the source CSV file it causes 14 changes to be registered on the corresponding adapter. Reflection then takes around a minute to run, with the Pending Changes counter counting going down one change at a time, and eventually completing successfully. I did have joined records with blank values until yesterday, but I’ve fixed that issue and performed many import all operations since then so I don’t believe it’s related. If I modify twelve records similarly then I end up with 168 changes, and it takes around two minutes to process with the Pending changes counter counting down in multiples of 12 this time.
![](/s/cache/7d/53/7d53b04c16d6ef66897d1a534be84eba.png)
Patch released with broker 5.3.4.0
Customer support service by UserEcho
Patch released with broker 5.3.4.0