This is mainly a question to determine if this expected behavior and if it is maybe a conversation about how it could be improved.
We have an unaltered SSIS Package created (not sure how many years ago) on a version of of CozyRoc prior to 2.2. The package is relatively simple in that it pulls a reference table from a Sharepoint list. The other source is a SQL table that is considered the authoritative source.
These sources are then run through a Table Difference step to delete/add or update the Sharepoint list based on what came from the SQL table.
The Sharepoint list is pretty simple with 4 fields, a Key Field, two fields that are 'compared' and the fourth is set to "use old". This package works as expected when run within the same version of CozyRoc. and existing, unedited items in the SQL table are preserved in the Sharepoint list.
Recently I began testing 2.2 and ran this package from my desktop, unknowningly the Table Difference step calculated that all of the existing Sharepoint list items needed to be replaced and new items created. While the data "looks the same' on Sharepoint, this causes an issue in our environment because we have a dependent Sharepoint list that "looks up' the values from the list CozyRoc is maintaining. All these lookups are broken by the recreation of the items.
I wasn't ready at the time to put 2.2 into production, so I fixed this by manually relinking each of the dependent items. This weekend we pushed 2.2 (updating from a build of 2.1) into production and unfortunately the same symptom has occurred with an entirely 'net new' list of items on the Sharepoint list, again breaking the dependent Sharepoint list.
Is this behavior expected when updating between versions of CozyRoc? Thanks!