Microsoft Dynamics CRM 2011 Instance Adapter – Part 7 – Sample Data Integration – Part 3

Colin Maitland, 20 May 2013

In this series of blogs I am writing about using the Microsoft Dynamics CRM Instance Adapter with the Connector for Microsoft Dynamics to integrate two Microsoft Dynamics CRM Organisations. 

In my previous blog: 

•  I wrote about the impacts of attempting to integrate Towns/Cities related to parent Countries that did not exist in the Destination Organisation. I mentioned the impact that the Business Required verses the No Constraint Requirement Levels on the parent Country field for Towns/Cities had.

•  I wrote about the impact of attempting to integrate Articles related to parent Subjects which did not exist in the Destination Organisation, and the impact that the System Required Requirement Level on the parent Subject field for Articles had. 

In this blog I will document some points regarding the setting of values for the Created On, Created By, Modified On, Modified By, Owner, Status and Status Reason fields. 

Created On

•  If the Destination Created On field is mapped to the Source Created On field then the Created On value for new records, added to the Destination Organisation, will be set to the actual date/time on which the new record was created in the Destination Organisation rather than to the date/time on which the new record was originally created in the Source Organisation. In other words, this mapping has not effect.

•  However, if you do not map the Destination Created On field and instead map the Destination Record Created On (Overridden Created On) field to the Source Created On field then the Created On value for new records added to the Destination Organisation will be set to the original date/time on which the record was created in the Source Organisation as long as the Destination Organisation’s Integration User has the ‘Override the Created On or Created By for records during Data Import’ privilege selected on one of its assigned Security Roles.

The following image shows the mapping of the Destination Organisation Record Created On field to the Source Organisation Created On field. 

The following image shows the ‘Override Created On or Created by for Records during Data Import’ privilege located the Business Management tab of a Security Role.



Created By

•  This is set to the Destination Organisation’s Integration User and cannot be overridden. Despite its name, the use of the ‘Override the Created On or Created By for records during Data Import’ privilege does not have any impact.

Modified On

•  This is set to the actual date/time that the record was created or last modified in the Destination Organisation and cannot be overridden.

Modified By

•  This is set to the Destination Organisation’s Integration User and cannot be overridden.

Owner

•  If mapped, then this is set to a Destination Organisation’s User or Team with the same Name as the owning User or Team in the Source Organisation. Whether or not the matching User or Team in the Destination Organisation is also in a Business Unit with the same Name as that in the Source Organisation is not taken into account. The key criterion is that the Name of the User or Team in both Organisations is the same. Other factors to consider are whether or not the User or Team in the Destination Organisation is Active and has the required privileges to own records. If a matching User or Team does not exist in the Destination Organisation then the Owner is set to the Destination Organisation’s Integration User.

Status and Status Reason

•  If mapped, then these will set to the same Status and Status Reason values as that from the Source Organisation as long as the corresponding Status and Status Reason values exist in the Destination Organisation.

In my next blog I will mention some other findings with respect to the creation, update, delete, deactivate and activate actions for records.