Updated solution for scheduling recurring Dynamics 365 workflows

I’ve released an updated version of my recurring workflow scheduler for Dynamics 365 Customer Engagement. This solution targets Dynamics 365 version 9, so it should work in all current Dynamics 365 online organizations. You can download version 1.3 of my solution from here: https://github.com/lucasalexander/AlexanderDevelopment.ProcessRunner/releases/tag/v1.3. For more information on the use of this tool, take a look at the original blog posts: »

Dynamics 365 Configuration Data Mover v2.4

I’ve released an updated version of my popular Dynamics 365 Configuration Data Mover utility that was built with .Net 4.7 to address the new requirement to use TLS 1.2 (or better) for connections to Dynamics 365 online instances as described in this entry on the Microsoft Dynamics 365 team blog: https://blogs. »

Using proxy connections with the Dynamics 365 Configuration Data Mover

I was recently asked to add a feature to my Dynamics 365 Configuration Data Mover to enable connections through a proxy server. Because the tool is a .Net application, proxy server connections can be configured directly in the AlexanderDevelopmentConfigDataMover.exe.config file. For example, if you want to use the default Internet Explorer proxy settings, just add the following values inside the element: »

A Dynamics 365 local message listener for web client notifications - part 3

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. »

Creating many-to-many associations with the Dynamics 365 Configuration Data Mover

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. »