About this block

Sync Conflict Resolver is a resolution queue for records where the connected CRM and the app both changed the same field since the last sync. The header counts 2 records that need a decision before the next Salesforce sync and offers an Apply default rule to all button. Each open conflict shows the record name, an object badge, and the conflicting field, then side by side Salesforce and Acme panels carrying each system value, who edited it and when, and a Keep this value button. The Q3 renewal close date row is already resolved and collapses to a single note that the Salesforce value was kept.

Conflicts are one const array with source and dest sub objects and a resolved flag that switches each row between the two panel layout and the resolved note. A footer spells out the default rule, keep the most recently edited value, and names the protected fields (billing address and close date) that always wait here for a manual call.

When to use

Reach for this block on an integration settings page or a sync review screen, wired to your conflict detection service. Show it before a scheduled sync runs so operators can clear blocking conflicts first.

A natural flow around it on an Application Pro page:

Before

• Sync status panel
• Settings pages

After

• Activity

What you can display

One strong use is the CRM field conflict queue. Other conflict resolvers:

• Calendar sync. Events changed in two calendars with the local and remote time side by side.
• Document merge. A shared doc edited in two places with each paragraph version and a keep action.
• Inventory sync. A SKU with different stock counts from the store and the warehouse system.

Tip: always show who edited each value and when; the timestamp is what lets an operator decide without opening the source record.