Several months ago 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 and shared some sample code for how to implement it. Recently I used this approach to establish communication between Dynamics 365 web resources and a fingerprint reader attached to a local PC. »
I’ve released an updated version of my popular Dynamics 365 Configuration Data Mover utility that includes the ability to create many-to-many associations in the target system. This upgrade is fully compatible with existing job files. To create a many-to-many job step in the GUI, select the new “many to many” step type and input a FetchXML query for the relationship entity (relationship entity name on the many-to-many relationship form) that includes the GUID fields for each entity. »
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. »