In this blog we show you how to create a build and a release pipeline in Azure DevOps that use one parameterized task group for deploying Azure Logic Apps and Functions to different environments.
After configuring the CRM Instance Adapter and an integration has been created, you can now generate Maps to define the transfer of data in the integration. Begin by selecting the integration you wish to add a map to by selecting it in the Connector and click the New Map button. A new dialog will appear that allows you to select an entity from both the source and destination organizations. After selecting the entities, click Create:
Before the newly created Map will work, we must configure how we want to map the entity’s fields. To edit a field mapping, click on the edit icon next to the field. There are three options to choose from:
There is one more option that makes it easy to use for bulk migration of the data. Instead of mapping individual fields, users can map all fields by using a back slash in the top level field. Doing so will then map all the fields from the source fields. This can also be accomplished by clicking the Edit button, selecting “Map to a source field” and then choosing the root element of the source field as well.
Once the fields are mapped, the Map Run Schedule must be set before activating. Select the map that you just created under the Maps root element in your integration. The page you’re presented with on the right side of the Connector screen should look like the following:
Modify the “Check for Changes” Edit hyperlink. Select the start time, and how often you want the adapter to check for changes. The recurrence patterns include options for “Once”, “Recurring”, “Weekly” and “Continuously”. Note that all integrations will make re-attempts at any failed entities.
After setting the “Check for Changes” value, we may also need to set what modified date the Adapter should check for. Clicking the second Edit link will allow you to pull records that have been modified since the date chosen. In most cases, the default value for this setting is several hundred years in the past.
Now that the scheduling of the map has been configured and the mapping rules have been put in place, we must click Activate button in order for it to be enable to run. We must then click the Save button to save all the changes made to the mapping. The next time the Connector starts, this mapping will be active and start pushing records across to the destination Dynamics CRM. Repeat this process for each entity you want to integrate. Before starting the Connector, make sure to check out our blog about Initial Integrations which contains useful information about both the order in which you integrate entities and also some special entities you’ll need to handle.