Showing posts from June, 2021

Custom Process Action vs Custom API in Dataverse

I recently had the opportunity to utilize the new Custom API functionality within Dataverse. I had previously used Custom Process Actions and was a little confused as to the difference and why i would want to use the Custom API functionality. After digging through the documentation I finally discovered the major difference is this… The use case I was working on only returned data to the user so the Custom API allowed me to create a Function rather than an Action. This made it much easier to test my API because i can just put the Url into the web browsers and see the results instance since it’s only a GET operation. There are some additional benefits to utilizing the Custom API as well such as being able to specify a specific security privilege. To see all the differences between Custom Process Actions and Custom API check out this article from Microsoft Headache Alert! Make Sure To Create Custom API Record Before Deploying Code On a side note, most of the articles I found a

Calling Dataverse Web API in PowerShell using Client Credentials

Connecting to Dataverse using PowerShell can be very helpful for data migrations and use within Azure DevOps. Connecting to an instance in a non-interactive way can be tricky though. This article will provide you the links you need for creation and App registration and adding the app user to your environment. You can then utilize the script provided to call Web API requests including ones you define using the new Custom API functionality now available. The script was written so that it is not dependent on any outside libraries such as the Microsoft.Xrm.Tooling connector. This is helpful in situation where involving an outside library will slow down your deployment time by having to be approved in a change control board. If utilizing an outside code library is not a concern you can create a connection to Dataverse utilizing the Microsoft.Xrm.Tooling connector Get-CrmConnection cmdlet. Create App Registration The first thing to do is create an App Registration within Azure AD for