Nishant Rana's Weblog

Using Custom Process Action with Code for integration – Dynamics 365 / Microsoft Dataverse

There are 2 ways to create a custom message in Dataverse, one is through action, and the other is through Custom API.

Check the post on Custom API

https://nishantrana.me/tag/custom-api/

https://nishantrana.me/2021/01/13/use-custom-api-to-create-custom-messages-in-dynamics-365/

Custom Process Action vs Custom API –

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/custom-actions#compare-custom-process-action-and-custom-api

With custom process action we can define business logic using a workflow, and we can extend it using either custom workflow activities or registering the plugin.

If we are just defining action just for the custom message and then using plugin/custom workflow activity for defining all the logic (and not using workflow), it is recommended to use the Custom API feature instead.

Here however we will have a look at the way we had implemented global custom action for integration with the external system for any inbound call to CRM.

Below is our sample custom global action with one input and output parameter.

For the output parameter, we are setting the value in the step.

Next, we have 2 plugin steps registered one on the pre-validation stage and the other on post-operation.

Pre-validation because we want to run the logic outside the transaction, perform validation, log exceptions, etc.

Pre-validation example –

https://nishantrana.me/2018/11/05/plugin-on-pre-validation-stage-in-dynamics-365-ce/

https://community.dynamics.com/365/sales/b/crminogic/posts/plugin-pre-validation-operation-to-show-an-error-message-as-well-as-log-the-error

Post-operation because action’s output parameter would only be available in the post-operation and used Shared Variable to pass the custom response from pre-validation plugin to post-operation.

On executing the action

We get the following plugin trace logs as expected.

One for pre-validation

Post-operation

Hope it helps..

Advertisements

Fixed: Action not appearing in Plugin Registration tool (Dynamics 365 / CE)

We had couple of actions created, but they were not appearing in the Plugin Registration Tool Plugin of XrmToolBox as shown below.

Refreshing the plugin, re-connecting to the organization, republishing the action, etc. didn’t work.

Eventually, we restarted the XrmToolBox and our messages started appearing.

Could be something related to Metadata cache.

Hope it helps..

Advertisements

Fixed – Unified routing was unable to provision error while trying to configure Unified routing

Recently while trying to set up Unified Routing, we got the below error.

“Unified routing was unable to provision. Please try again or contact Microsoft Support”

The user had the system administrator role and we already had the global administrator’s consent, which should be good enough to set up unified routing.

We tried with different system administrator users but that doesn’t resolve that error.

Eventually, we tried the setup with the same user but in a different VDI (Virtual Desktop Infrastructure), and the setup worked properly without any error. One probable reason could be, that the appropriate URLs being accessed during setup were already whitelisted in the other VDI, which wasn’t the case in the first VDI where we were trying.

Hope it helps..

Advertisements

Fixed – We couldn’t load your user roles from the selected Dynamics 365 Organization error while trying to set up Microsoft Dynamics 365 Marketing

Recently while trying to set up Microsoft Dynamics 365 Marketing on an existing Dataverse environment, we got the below error.

“We couldn’t load you user roles from the selected Dynamics 365 Organization. Please try again”

The user had the system administrator role, which is good enough to set up marketing.

We tried replicating the same in other trial environments but were not able to replicate the above error.

Hope it helps..

Advertisements

Transform your Model-driven app to a multi-session app using settings solution component

Another awesome “settings” trick from the author..thanks Mehdi

XRM Tricks (Power Platform & Dynamics CRM )

This blog will discuss new component added to Power Apps. It is about the “Settings” component. Indeed, this component allows adding a configuration layer for a model-driven application. This allows to easily activate or deactivate a feature for a model-driven app.

For more information on this component, I invite you to read this excellent blog from Power Apps team

Scenario:

Enable app makers to transform a classic model-driven app into a multi-session one using the settings components. You can check out the demo at the end of the blog before continuing reading.

Step 1: Create the Setting Definition

First, create a solution through make.preview.powerapps.com. Yes, we will implement everything on the preview version of PowerApps. Then, create a new setting definition. In my case I named it “Enable Multi-Session Feature” and applied the following values:

Step 2: Implement the logic

Let’s go back to the initial needs. The goal is…

View original post 271 more words

Dynamics CRM: Create Custom Autonumber Plugin Using Azure SQL Sequence

Temmy Wahyu Raharjo

In this blog post, I reviewed the Auto Number attribute that already can handle the common scenario. There is a way to give a simple conditional Auto Number from Nishant Rana that you can read here. But what if we want to implement a more complex scenario to generate the Auto Number part for instance we want to generate Auto Number based on Type? For example, if Order Type A, generate A001. If Order Type B needs to generate B001? The possible solution is to create our own code. So today we will try to create auto number code using Azure SQL Sequence (Sequence can ensure every call will get unique value).

Create Azure SQL Database

You can go to your portal.azure.com >SQL databases> hit+ Createbutton > fill theSubscription,Resource Group, fill theDatabase name, createServer.

For…

View original post 876 more words