GitHub user gertwieland added a comment to the discussion: Synchronize after merge: "Cannot insert null" into primary key
So I think I have a replication path. Set the primary key to nvarchar (any string I guess, but not integer), and try to run multiple copies of the "synch after merge" transform. It may work at first, but ultimately it will start throwing errors like "cannot insert duplicate into PK" or "cannot insert null into PK" Even when you then try to only run one instance of the Synchronize after merge transform, the error will persist. Then, set the PK to Integer (and obviously, pass an integer). Now it works again. Then, even if you revert the PK back to nvarchar, it works properly now. I'm attaching the pipeline I built for testing. [ [Merge_Sync_Test.zip](https://github.com/user-attachments/files/20966145/Merge_Sync_Test.zip) ](url) GitHub link: https://github.com/apache/hop/discussions/5444#discussioncomment-13607913 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
