I’ve released an updated version of my popular Dynamics 365 Configuration Data Mover utility that includes the following features: Path to source and target JSON data files can now be absolute or relative to current working directory. This is particularly useful for running the CLI tool in an automated fashion. Location of job configuration file can be passed to CLI tool as absolution or relative path. »
My Dynamics 365 Configuration Data Mover utility allows you to run synchronization jobs from an interactive GUI tool or the command line, but the actual data synchronization logic is contained in a separate AlexanderDevelopment.ConfigDataMover.Lib.dll file that can be included in other applications. In today’s post I will show how you can set up an Azure Function to execute a Configuration Data Mover job file to sync data between two Dynamics 365 organizations. »
In part one of this series, I discussed an approach for passing notifications from local applications to the Dynamics 365 web client through a message listener process that runs on an end user’s PC. Today I will show the code I used to build the message listener and the code to consume notifications in Dynamics 365. »
One problem that comes up from time to time on Dynamics 365 Customer Engagement projects is how to receive notifications from an application running on a user’s local PC. Although the Unified Service Desk (USD) interface supports a variety of ways for Dynamics 365 to interact with local applications, the out-of-the-box web interface does not. »
About two weeks ago a commenter mentioned that my Configuration Data Mover wasn’t working with UK Dynamics 365 online organizations that had been created since the change to the orgname.crm11.dynamics.com URL structure. I’ve released a new version with an updated SDK reference that has resolved the issue. If you are using an older version of the data mover and you are working with online orgs in a new region, you may want to go ahead and upgrade to the latest version here. »