If you have made it this far then kudos to you! This is the final post in this series and will just wrap up some final items regarding Scribe Online and the integrations.
While monitoring the Scribe Online Execution Logs for the solution, we should be able to see the map processing and hopefully succeed.
Now that CRM can run the Scribe Online map, we can utilize the IntegrationHelper class to build the rest of our integrations for the entities in CRM that we need. Since we passed in the RecordId parameter of the entity, we can use that with a Lookup block to retrieve the Account record from CRM and the desired fields with it, and allowing us to build out the rest of our map.
If the client wanted to make changes to the maps in Scribe Online, they could modify the existing ones or create new maps and change the Endpoint URL in CRM for the associated key. This would allow the user to copy the existing map, modify it as needed, and test it out without affecting the original map.
One of the benefits of having this CRM Workflow – Action – Plugin setup is that the integrations can be run On-Demand, if enabled. Rather than doing complex field changes or triggers, the user can just run the workflow from the “Run Workflow” button in the ribbon to test integrations and monitor their progress in Scribe Online.
Hopefully this will allow you to build your own integrations using Scribe Online from Dynamics CRM or any other source system. Utilizing this process, it creates a separation of CRM processing to Integration processing and makes it easier for the client to manage without learning C# / Custom Development.
Comments