I have two datasets to compare: an original table and a revised table. I want to pass them through the UpdateDetector to track Updates, Inserts, and Deletes. The two tables are linked by a shared primary key attribute, and I want to track changes that may exist in another attribute; however, the original table has an extra attribute, ExtraID, which does not exist in the revised table. For features that exit the Updated port, this ExtraID loses its value. How do I retain the values in ExtraID and prevent them from exiting the UpdateDetector as NULL?
Best answer by nathanatsafe
View original