Skip to main content
  • EN

My workspace is using ChangeDetector with two data sets original and revised. It appears that if the revised records contain two records with the same key and selected attribute and this key does not already exist in the original table then ChangeDetector will want to insert both records in the original table. This happens when the key is not already in the original table before the run. On subsequent runs, ChangeDetector finds the key and selected attribute in the original table, and it behaves as expected and does not insert a record. It treats it as an update or unchanged. How should I account for this? Attached is an image of my workspace. Thank you.

 

If there are two records with the same key, that will likely be a problem.  The key should be unique.  If the 2nd record is an exact match of the first record, you can use DuplicateFilter to ignore the 2nd record.  If the 2nd record is not an exact match and you need both records, you may want to use a different key that is guaranteed to be unique.

Reply


Community Stats

30,102
Posts
114,260
Replies
37,733
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.