Two systems editing data does not mean synchronization is resolved
Before moving data, decide who is authoritative for each field and what happens when both sides disagree. Think² organizes collaborators with groups, context, an optional computer per collaborator, compatible models, and authorized tools; these examples are not verified connectors or an executed synchronization.
Waitlist: no guarantee of immediate access or a free plan. Destination currently in Spanish.
Situations to review
A list is the authoritative reference for certain CRM fields
Define a direction for those fields and keep the list authoritative. Local CRM changes do not flow back merely because they exist.
One-way means a defined direction within that scope; a one-time import does not establish continuous updates or subsequent reconciliation.
Sales and operations have legitimate changes on different sides
Define authority field by field and map identities before considering both directions. If both edit the same field from the same reference version, apply an authorized resolution or stop for conflict review.
Two-way does not mean the last received message wins. A newer clock value or latest delivery confers no authority or guarantee of actual edit order.
Duplicates, a deletion on one side, or unknown outcome after an attempt
Stop uncertain identities; distinguish proposed deletion, rejection, attempt without response, and confirmed state. Define loop detection and evidence needed for reconciliation without blind repetition.
Do not infer success from no error or propagate deletion automatically. Approval is not execution; an unknown state requires checking evidence before retrying.
Waitlist: no guarantee of immediate access or a free plan. Destination currently in Spanish.
How to evaluate the work
- Create a field/system/authority/authorized-editor matrix. Choose which data travels in each direction and what stays out. A business instruction does not itself narrow provider-granted permissions. Decision matrix: use one direction per field when one source is authoritative and the destination must not return edits; consider both directions when both systems support legitimate edits and an explicit field-level rule exists; if identity, version or conflict resolution is missing, leave the exchange pending rather than enabling both directions. Choosing a direction does not establish provider support for implementing it.
- Map identities with explicit keys and scopes; check duplicates, nulls, and transformations. Similar names do not prove the same person or entity. Define the reference version and equivalence criterion per field before reconciling.
- Specify conflicts, deletions, loops, versions, and unknown states. If-Match uses strong comparison: a specific ETag expresses a precondition on the representation; “*” checks existence, not a specific version. The API must support and apply it before the method; rereading then writing without conditional control leaves a concurrency window. Microsoft Graph delta is pull-based for supported resources, not two-way synchronization by itself; repeats, delays, and responses without an assumed order may occur. No endpoint was tested here. Check resource-specific limits: change tracking differs, and a field-by-field strategy does not permit legitimate editing of every field on both sides.
Reusable template: record/scope/identities; field; authority; base/observed versions on both sides; direction; conflict/decision; deletion/loop rule; proposed change; specific prior approval; attempt/result/evidence. Fictional example: CRM K17 and address book A09 represent one record under a teaching-only mapping. Base email: uno@example.invalid. CRM changes to dos@example.invalid and address book to tres@example.invalid before reconciliation.
CRM is declared authoritative, but this policy requires reviewing a double change: do not overwrite or send. Only the conflict is described; no real query, write, retry, synchronization, or Think² test occurred. One decision does not authorize future unreviewed external actions. Proposed manual output: record K17↔A09; field email; base uno@example.invalid; changes dos@example.invalid and tres@example.invalid; declared authority CRM; status REVIEW because both sides changed; proposed write none; real outcome not observed.
Declared authority does not remove this fictional policy's review requirement. After a decision, versions would need checking again before an authorized attempt.
Frequently asked questions
When is one direction enough?
When one system is the reference for shared fields and the destination receives them without returning its changes to that source. Other fields may have different authority; declare that scope.
When should both directions be considered?
When both sides have legitimate changes and identity, field-level authority, and conflict resolution are defined. Otherwise another direction does not automatically improve reliability.
Do If-Match or delta guarantee both systems match?
No. If-Match conditions a method if supported and applied by the API; it does not resolve identity, authority, or the rest of the workflow. Delta queries supported-resource changes within its limits; it does not create reverse flow or a push guarantee by itself.
Sources and scope
- RFC 9110 — HTTP Semantics, 13.1.1 If-Match — Historical direct verification on 13 November 2026 of section 13.1.1: strong comparison, existence wildcard and evaluation before the method. The 16 November extraction stopped at 6.4.2 and did not reach 13.1.1. Not proof of API or Think² implementation.
- Microsoft Graph — Delta query overview — Pull model, supported resources, repeats, delays, no assumed order; not an integration or complete two-way flow.
Keep exploring
Waitlist: no guarantee of immediate access or a free plan. Destination currently in Spanish.