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. »
I’ve previously showed how to access online and IFD instances of Dynamics 365 Customer Engagement from Python code. Because that sample code authenticated to the Web API using OAuth, it won’t work with on-premises instances. Recently I’ve been doing some work with Python and an on-premises Dynamics 365 organization, so I thought I’d share a sample that shows how to authenticate to the Web API using NTLM. »
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: »
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. »