Dynamics CRM is a widely used cloud CRM from Microsoft, focused on Sales, Marketing, and Service (help desk) sectors. Skyvia supports importing data to and from Dynamics CRM, exporting Dynamics CRM data to CSV files, replicating Dynamics CRM data to relational databases, and synchronizing Dynamics CRM data with other cloud CRMs and relational databases.
Replication with incremental updates and Synchronization delete records, deleted in Dynamics CRM, from the target database only if auditing enabled for the corresponding entities. To start auditing, in the Dynamics 365 Navigation Pane, click Settings. Then under System, click Auditing. In the Audit area, click Global Audit Settings. After this, in the System Settings dialog box, click the Auditing tab. Then select the Start Auditing check box. For more information about Dynamics 365 auditing, see The CRM Book or Dynamics 365 documentation.
When the not equals operator is used in filters for Dynamics CRM, records with an empty (null) value in the compared field are also returned. This behavior is different from the behavior of this operator for database, but this is the normal Dynamics CRM behavior.
Dynamics CRM object can have a reference field that can reference different object types. For example, the Contact object has the parentcustomerid field, which can reference another contact object or an account object. For such fields, Skyvia displays an additional field with the name of the reference field with suffix '$type' added. For the parentcustomerid field it would be parentcustomerid$type. When loading/exporting data from Dynamics CRM, this field value will be a name of the referenced object type. When loading data to Dynamics CRM, this field determines the type of the referenced object. If the reference field is a required field, this virtual field is also required.
Note that Skyvia does not support such polymorphic relations between objects. It means that when you export an object, the fields of related objects that are referenced by such fields cannot be added to export. And you cannot add related objects that are referenced by such a field when performing one-to-many import or synchronization.
Additionally there is a limitation on restoring such relations from Backup. Skyvia can correctly restore such relations only when the reference field is not required and is updatable.
When backing up the Dynamics CRM connections object, you need to note the following. When creating a record in the connections object, two records for both directions are actually created. This means that when records are restored from backup, duplicates may be created. In order to avoid creating duplicates when restoring connections, restore only the records with IsMaster=True. Actually, you may back up only the records with IsMaster=True for this table. For this, when creating a backup package, after selecting the connections table, click the edit link and specify the corresponding filter condition.
To connect to Microsoft Dynamics CRM you need to specify the URL to connect, user name (Windows Live ID), and password for your Windows Live ID account.
You need to specify the following parameters for a Dynamics CRM connection:
|•||URL - the url that you use to connect to Dynamics CRM. Usually it looks like: https://companyname.crm.dynamics.com|
|•||Username - your Windows Live ID.|
|•||Password - the password for your Windows Live ID account.|
|•||Metadata Cache - Determines how often to update cached metadata for the connection. By default, Skyvia caches metadata of available objects for cloud sources. You can configure how often the cache is refreshed automatically or reset in manually on the Connection Details page of the corresponding connection by clicking the Clear link in the Metadata cache parameter in the Parameters pane. The following values are available for this setting:|
|o||Disabled - the metadata cache is not created, and metadata are queried automatically whenever the connection is opened.|
|o||One Hour - the metadata cache expires after one hour since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||One Day - the metadata cache expires after one day since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||One Week - the metadata cache expires after one week since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||One Month - the metadata cache expires after one month since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||Infinite - the cache is never reset automatically. Default value.|