Do you want to share more about collision detection? Last write wins? I assume it's harder when things are being synced in the background on a schedule.
Each sync in Polytomic is one-way so we're not forced to deal with collisions all the time.
But you can, on a per-field basis within a sync config, declare that field not to be synced if the destination system already has a value in the corresponding field.
This setting is a proxy for deciding where your source of truth is for each field if you are indeed setting up two-way syncs.
Most customers are pulling data into their data warehouse, then syncing from queries that generate other values back into other systems. This issue doesn't come up there. But customers of ours doing two-way syncs between, say, HubSpot and Airtable or such do need to decide where the source of truth is for each field.
Each integration is supported as both a source and a destination. So you can have two one-way syncs set up between systems A and B, thus moving data in two directions.
