Unintended bidirectional sync between MSSQL and Shopify using constant mapping
I can't achieve a one-way synchronization using the constant mapping. Any help or suggestion is greatly appreciated.
Setup:
- Source: MSSQL products table
- Target: Shopify products
- Sync Field: A field named Sync in the MSSQL table, set to True for all rows. This field is used for constant mapping to ensure synchronization only flows from the SQL table to Shopify, not the other way around.
Configuration:
- Target to Source Mapping:
- Source's Sync field mapped(constant mapped) to the Target (See first image)
- The Sync field is set to False.
- The "use this value as the filter of target records" option is checked to ensure synchronization only occurs from source to target.
Issue:
To verify if changes made in Shopify are reflected in the source, a single product attribute in Shopify is modified. However, upon running the Sync task, synchronization occurs in both directions instead of the intended one-way sync. Specifically, this results in:
- Three rows in the source table being updated, with new values (like time and productids) inserted along with the single change that was made in Shopify.
- The Sync field value in the SQL table changes to False after the run.
Additional Information:
- This issue has only recently surfaced. Approximately two weeks ago, multiple successful one-way synchronization runs were completed without any issues.