The purpose of this article is to provide direction to Outreach Admins in understanding the functionality of the Microsoft Dynamics Conflict Resolution Layer.
Microsoft Dynamics is a CRM created to store customer data. Outreach is designed to optimize the way sales teams sell. Since a CRM is an integral part of the sales process, Outreach works with Dynamics seamlessly to sync sales reps' activities and tasks back into the system of record, Dynamics.
Building The Conflict Resolution Layer in Outreach's Dynamics Integration
The concept of a conflict resolution layer isn't found in many platforms. They typically decide one platform's data is more important than all the others. Without this layer, if changes are made in two platforms before a sync can occur, the hierarchy determines whose data wins. This means that data gets overwritten, you lose valuable information, and there's no going back from that.
The conflict resolution layer looks at both Outreach and Dynamics to see if updates were made in both locations. It acts as a middle layer that instantly compares both records. If there are updates in both platforms, the plugin ensures all updates are made so the data matches. It only updates the fields that have changed and never overwrites data that doesn't need to be updated. Your data deserves better. That's why Outreach has an intelligent layer to handle conflicting updates between Outreach and Dynamics based on the way your team makes updates to records.
Outreach has created the most intelligent data conflict resolution layer in the game! You no longer need to worry about data entry overrides from the systems which fee Dynamics with data. Whether you are updating data in and out of Dynamics, only one direction, or interested in overriding blank fields, Outreach can accommodate. You can always trust that you're looking at the most up to date, accurate data, whether you're in Outreach or Dynamics.