IntegrationAdvancedmdmlockingsync
Implement semantic locking for bi-directional Salesforce MDM sync conflicts
Real World Scenario
Sales rep and MDM steward simultaneously update Account industry field; last-write-wins loses compliance-approved MDM value.
Expected Answer
• Semantic lock: MDM-owned fields reject Salesforce overwrite without steward release
• Lock metadata field map Integration_Field_Owner__mdt
• Conflict queue UI steward resolves with audit
• Timestamp vector clock optional for distributed ordering
• Integration respects lock flag in inbound API validation rule
• Temporary lock during MDM batch enrichment window
• Metrics conflict rate drives field ownership review
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Semantic lock: MDM-owned fields reject Salesforce overwrite without steward release. Lock metadata field map Integration_Field_Owner__mdt. Pick based on your integration pattern and team capability. Bi-directional sync needs field-level authority not org-level last-modified-wins. Optimize for scale and operational observability.
Architect Perspective
Bi-directional sync needs field-level authority not org-level last-modified-wins.