When your CRM and Airstride both change a deal, the newer edit wins. CRM Sync Conflicts shows you every time that happened, both values, and which one is now live.
Open CRM Sync Conflicts in the Workspace group of the sidebar. A row is added when a change from your CRM contends with a more recent edit made in Airstride. If that has not happened, the page says No sync conflicts.
The table is wide, so on a small screen it scrolls sideways. It has eight columns.
Start with Changed Fields. Each field shows the CRM value and the Airstride value, with a tag for the side that is now live. CRM applied means the CRM value was written to the deal. Airstride kept means the deal held on to its own value and the CRM value was set aside.
Outcome sums up the row. Inbound Won means the CRM edit was newer. Airstride Won means the Airstride edit was newer. The two Last Modified columns are the timestamps behind that decision, so you can check it yourself.
If the CRM replaces a deal value that someone set in Airstride, that person gets a notification: the deal name, which CRM it came from, the value they set and the value that replaced it. Open the deal from the notification to review it.
The conflict page itself has no resolve control. If the wrong value is live, edit the deal value again, in Airstride or in your CRM. A new edit is a new, more recent change, and it is the one that counts next time the two systems compare.
No. CRM Sync Conflicts is a read-only record. Airstride decides by timestamp, and the page shows you what it decided. To change a value, edit the deal.
When a change coming in from your CRM contends with a more recent edit made in Airstride. If nothing contended, nothing is recorded, and the page says No sync conflicts.
The Object Type column is built to hold more than deals, but the conflicts recorded today are deals.
Vendor users who can read deals, in the Workspace group of the sidebar. Partner users do not see it, and a partner who opens the address is told they are not authorised.
The person who made the edit, and only them, with a notification titled with the deal name and where the value came from. If a partner user made the edit, their notification does not include the amounts. Edits made through an API key have no person to notify, so no notification is sent.
No. A failed load shows its own message and a Try again button. No sync conflicts appears only when the page read the feed successfully and found nothing.
Twenty per page, with page controls under the table.
We will connect your CRM with you on the call and show you what a conflict looks like when it happens.
