Much awaited, the ability to query the CDS / Dynamics 365 using SQL is now finally in Preview.
This article is not about what DES is, or how to configure it. You will find literally a thousand articles about that by running a quick search. Instead, I want to focus on some of the scenarios where this makes sense to use.
Now you can concatenate record names or any other fields from values in other fields or fields of related records in minutes. Gone are the days of custom code.
What’s that going to do? Well, it takes a solution named solutionName and exports it in an unmanaged form to the specified path.
In this part we’re looking at connecting to a D365 environment. Just like we did with the first part, we’re putting the connection code in a function. We’re doing this in order to be able to call it multiple times, depending on the environment we’re connecting to. Eventually, we’ll connect to both a source and a target environments.
Right off the bat, we’re looking at the Microsoft.Xrm.Data.PowerShell library. It’s available from GitHub
Will this UI change impact your current business processes? Moving the Write-in Products to be buried down could make a difference in your user's experience.
The way to capture the form input and send it to your Dynamics 365 instance is by way of Flow. Let’s have a quick look