In part two of this blog series, we examine the role of technology in enhancing the customer experience in government with a focus on streamlining and automating customer-facing processes.
Once you have tested your adapter settings, you can use the CRM Instance Adapter Configuration Utility.
The CRM Instance Adapter Configuration Utility is accessed by going to the Adapter Settings window, selecting the endpoint you wish to configure and clicking on the Configure Microsoft Dynamics CRM link.
The first window of the configuration utility will pull the credentials from the adapter settings over and give you a list of all available organizations for those credentials. Select the organization you wish to configure the adapter for and click the Configure button:
The next window in the configuration utility displays all entities available for integration with the CRM Instance Adapter. Entities that are checked already have object provider configuration files generated for them. You can select whichever entities you wish you to configure in this window and then select Next. In the following window, you’ll notice that we’ve selected all available entities by clicking on the Select All button:
Now that we have identified which entities to include, we are ready to start the configuration.
On the next window, click Configure. You can watch the utility status window as the utility creates the necessary object provider configuration files for each entity. Click Finish when the process has completed and the button becomes available:
These XML configuration files are stored in C:Program Files (x86)Microsoft DynamicsMicrosoft Dynamics AdapterAdaptersMicrosoft.Dynamics.Integration.Adapters.DynamicCrmObjectConfig under the respective endpoint and organization. One file is created for each entity in the process.
When we navigate to the ObjectConfig folder, you’ll notice that the two endpoints are represented there:
Drilling into one of our configured endpoints, we see that there is a folder representing each organization we’ve configured:
Drilling once more down into one of the organizations, we see a list of object provider configuration files that have been created for us:
Once you finish creating the configuration files, the adapter is ready for mapping the entities. You must use the configuration utility for both Destination and Source adapters for the Connector to work. To start working with the configuration files we’ve just created, see our blog on generating mappings for your integration next.