Setup Chat channel– Omnichannel for Customer Service

In the previous post we saw how to provision the Omnichannel for Customer Service, below are some of the basic steps we will follow to set up Chat channel

  1. Assign Omnichannel security roles to users.
  2. Create Queue(s) and add the users to the queue.
  3. Create a Work Stream of type Live Chat.
  4. Create a new Chat Widget using the Live Chat Work Stream.
  5. Specify pre-chat survey in Chat Widget which will be used for routing rules.
  6. Specify Routing Rules in Live Chat Workstream.
  7. Embed the Chat Widget snippet code in the portal.
  • Assign Omnichannel security roles to users

There are 3 security roles specific to Omnichannel.

  • Omnichannel administrator
  • Omnichannel agent
  • Omnichannel supervisor

Here we have assigned the Omnichannel agent role to the users.

  • Create Queue(s) and add the users to the queue

Within the Omnichannel Administration portal, navigate to Queue.

We have created a complaints queue and added “test user 2” to it.

Similarly, we have created another queue for inquiries i.e. Service Request queue with priority 2 and added user “nishant rana” to it.

  • Create a Work Stream of type Live Chat

We have created a workstream of channel type Live Chat with default values for other options.

  • Create a new Chat Widget using the Live Chat Work Stream

Navigate to Channels à Chat and create a new chat.

Here we have created a new chat widget specifying the work stream we had created earlier. Note the code snippet section which will be used to embed the widget in the portal.

  • Specify Pre-chat survey in Chat Widget which will be used for routing rules in the workstream

Navigate to Pre-chat survey tab in the widget and set Pre-chat survey as Yes.

Click on Add question to capture user’s response to be used within routing rules.

Below in the question we are asking user’s choice for either Enquiry or Complaints.

  • Specify Routing Rules in Live Chat Workstream.

Open the My Live Chat WS work stream created earlier, select the Routing Rules tab.

Click on Add to add the routing rule.

For Request Type equals to “Enquiry” route it to “Service Request Queue”

Similarly create a new routing rule item record, for Request Type equals to “Complaints” route it to “Service Request Queue”

We now have 2 routing rules defined for our 2 queues in the workstream.

  • Embed the Chat Widget snippet code in the portal

Navigate to the widget created earlier and copy the code snippet.

Here we are embedding it in the Chat Widget Code – Content Snippets in Portal.

Clear the cache in the portals if needed.

Login to the Omnichannel for Customer Service app with the agent’s login.

In the portal, customer has selected Enquiry and clicked on Submit to start the chat.

The agent receives the notification.

Accepting the notification opens the conversation window for the agent.

Agent can start communicating with the customer.

Different options that are available for the agents.

Below we have embedded the chat widget code in an HTML page and have started the conversation by selecting Enquiry as the option.

The agent will receive the notification, while he is still having a conversation with the other customer. This is governed by routing rules and capacity defined for the agent and the work stream.

Below we can see the agent in conversation with both the customers.

Thus, we saw how easy it is to set up the chat channel in Omnichannel for Customer Service.

Refer below blogs to learn in-depth about the Omnichannel

along with Microsoft Docs

Hope it helps..

Every PowerApps Formula You Ever Wanted To Know As A Functional Consultant

A very handy guide for #PowerAddicts

DIY D365

Hello Readers

This blog is to help fellow consultants to start their journey on PowerApps. We all know how easy it is to put together a screen on Canvas Apps but as and when we need a specific action on it or from it; we fall short of formulas/functions. That’s because we never required these formulas in Model Driven Apps.

But as Business/Functional Consultant, you want to deliver value to your client, make their life easier, Don’t you?

I am sure you do, so here I am providing you with 20 essential functions you must know as a functional consultant. This can be a starting point for you; well, Microsoft is trying hard for Business Users and Functional Consultants to get in the rink of Power Platform. Their learning path is specially designed for Business Users and Functional Consultants, check it out here Learn PowerApps.

All formulas below are…

View original post 504 more words

Admin Center URL(s) in Microsoft Dynamics 365 ( Power Platform)

Listing down Administration Center URL(s) for quick reference à

Admin Center URL
Microsoft 365 Admin Center

Power Platform Admin Center

PowerApps Admin Center

Dynamics 365 Admin Center

for e.g.



North America


Replace <region> with

Dynamics 365 Advanced Settings https://[orgname].[region]

Dynamics 365 Home

Power Apps Maker Portal

Power Automate Admin Center

Power BI Admin Portal

Azure Active Directory

Hope it helps..

Overcoming unprecedented business challenges with Microsoft Dynamics 365

In such unpredictable and challenging times, organizations must make sure they’re getting maximum value and efficiency from their Microsoft Dynamics 365 investment.

Through this blog and social media, I’m passionate about sharing my knowledge and helping other Dynamics users get the most out of the platform. That’s why I was excited to contribute to Nigel Frank International’s new white paper Overcoming your business challenges with Microsoft Dynamics.

To help Dynamics customers navigate these unprecedented waters, 16 Microsoft Dynamics 365 professionals and experts shared their thoughts on topics such as cutting costs, ensuring business continuity, data security in Dynamics, growing at scale, and how to make the most of remote working.

The result is over 65 pages of practical advice and actionable tips to help users of all Dynamics apps are fully utilizing their CRM or ERP and taking advantage of its functionality, scalability, and flexible nature to ensure the continued success of their operations.

With more people than ever working from home or on personal devices, I believe the advice on data security is particularly relevant today. In this section of the white paper, Dynamics 365 experts address the new and increased security risks that can arise as growing numbers of Dynamics users access the platform remotely. You’ll find many tips and tricks on how to safeguard your Dynamics data, tools to use to step up your security levels, and how to equip users to work safely in the face of this new normal. 


You can download the white paper here—I really hope you find it useful!

Provision – Omnichannel for Dynamics 365 Customer Service

For one of our projects we are exploring capabilities of Omnichannel.

Below are the steps for provisioning the Omnichannel for Dynamics 365 Customer Service for quick reference.

First, we need to make sure we have the Customer Service Hub already installed.

Next, we need to have an active subscription of Chat for Dynamics 365 Customer Service or Dynamics 365 Digital Messaging

The other options

Navigate to Microsoft 365 Admin Center

Select Purchase services

Select Dynamics 365 Customer Service Digital Messaging Add-on trial.

And also assign the add-on license to the users who need to work with Omnichannel Service.

Login to Data access consent URL using the Global Tenant Admin account and give the consent.

We’d be presented with the below message.

Login to Dynamics 365 Administration Center and navigate to Applications Tab and click on manage for Omnichannel for Customer Service.

This opens the Manage environment page for Omnichannel.

Click on Add Environment to add the environment.

Here we can select the environment to which we want omnichannel solutions to be configured.

Click on next and we can then add chat as one of the channels.

Click on Next to similarly setup SMS, Social, and Microsoft Teams as the channels.

Click on Finish to start the installation.

It will show the status as Installed after some time. (took around 1 and half hour in our case)

To manage the channels or delete the omnichannel we can use the same Manage option for Omnichannel for Customer Service in the Applications tab within Dynamics 365 Admin Center.

We can use the Delete button to remove the Omnichannel configuration à

We’d also see the Omnichannel Administration and Omnichannel for Customer Service apps in the list of Dynamics 365 Apps.

Get all the details here

Hope it helps..

Setting up default authentication provider in PowerApps/ Dynamics 365 Portals using identity provider configuration UI

All about Dynamics 365, PowerApps, Power Platform and Power Apps portals by Debajit Dutta

In this blog, I will set-up the default portal authentication provider using the new PowerApps/ Dynamics 365 Portal identity provider configuration UI. If you are not aware of the preview feature, please visit the previous blog to know more about this new preview feature.

So below is the identity provider screen.


And by default, Azure Active directory and Local sign in is enabled. Say we want to enable Azure Active Directory as the default authentication. Before this UI, came into effect we needed to create some site setting configurations to do the same. But now it’s quite easy. All we need to do is click the three dots in Azure Active Directory and mark it as default


You will get a confirmation box. Just click OK.

Once done, you will see a tick in pink with the associated provider which basically means it is the default provider.


What exactly happened…

View original post 136 more words

Multi-Currency in Dynamics 365

Multi-currency was introduced in the product with version 4.0

Thought of just revisiting it as we were recently having certain requirements around it.

Below are few points for quick reference  (Nothing new, as most of the things remains the same with Multi-currency in the product) à

  • There can only be one Base currency that can be defined while setting up the organization or the instance. The base currency cannot be updated.
  • To define additional currency, navigate to Settings à Business Management

By default, we can see 18 currencies defined.

  • We can create additional currencies either system or custom.

For system currency, we can select any of the existing currency code.

If we do not find our currency in the system, we can define Custom Currency

  • Through Set Personal Options, the user can specify default currency

The default currency will be set as the currency for the user while creating a record as shown below.

  • The base amount is calculated after the record is saved.

The calcuation considers the Exchange Rate defined in the Currency record.

  • Exchange Rates are not updated automatically. We should have some mechanism in place to update the exchange rate.
  • The base amount is re-calculated if the money field in the record is updated or state of the record is changed.

E.g. we have updated the exchange rate to 25.

The record still shows the old base value.

Here updating any of the currency fields will trigger the recalculation.

Below we have updated the value for the Actual Revenue field and saved the record which triggered the calculation for the base fields using the new exchange rate defined.

  • We can write a console application or SSIS packages that will update the money field of the existing records, whenever the exchange rate is updated to trigger the recalculation of the base currency field if needed.
  • Create a new currency field for an entity will create a corresponding base currency field. It will also create Currency and Exchange rate field if this is the first currency field created for the entity. Any subsequent new currency field created will not create the currency and exchange rate field.

  • Updating the status of the record will also update the base currency as shown below.

Below are some of the helpful articles with regards to currency and exchange rate in Dynamics 365.

  • Using Power Automate to update the exchange rate

  • Exchange Rate Control in PCF Gallery

  • Update exchange rate through a Console app

  • Through XrmToolBox plugin

  • Using workflow and dialog (deprecated)

Hope it helps..

Few points to consider -Status Reason transitions in Dynamics 365

We can specify Status Reason Transitions for Case as well as custom entities. Using the status reason dialog box, we can define (filter) which values are available to be set as next status reason.

Let us take a scenario where we have the following values defined for Status Reason for Active State in a custom entity named Test Entity.

Just to keep it simple we have a just on transition defined i.e. from A1 we can only select A2.

So now when a user creates the Test entity record with A1, the only other option user can select is A2.

Now let us try updating it through backend and set value as A3 for the same record with value A1 as status reason. (Here we have used SQL 4 CDS plugin)

Well, it updates the record with value A3 and doesn’t throw any error.

This would make us think that it only works from the client side and will not work from the server side.

Let us now create a workflow to update the value to A3.

Let us update the subject of the record to trigger the workflow for the below record.

Interestingly we get the error and are not able to set it to A3 as expected.

That was with the real-time workflow, for the asynchronous workflow also we get the error.

Let us give it one more try and update it through service.

Through the service call, we can update it.

So basically, the State transition rules will work as expected from user interface and workflows, however, through service we are still able to override it, which we need to be aware of before using this feature.

Hope it helps..

Sample Decision Matrix Template for Single vs Multi Instance – Dynamics 365

Deciding on a single instance or multi instance is a difficult process, specially for an Enterprise Customer, as each has its own share of pros and cons.

Sharing a sample decision matrix that could help us to decide on single versus multi-instance.

Download it here –

Also check the below post for more details

Single vs Multi-instance – Points to consider

Hope it helps..

Differences between Subject and Category Entity in Dynamics 365

Subject entity \ feature has always been an integral part of Dynamics CRM at least since 3.0.

It gives a nice hierarchical way of organising and maintaining information.

To create or update Subject, navigate to Service Management area.

Similar to Subject entity, Category entity was introduced in CRM 2016 Update 1 (Service Pack 1 – On-Premise).

Navigate to Service Management area, to work with Category entity.

  • Can we customize Subject or Category Entity?

We cannot customize Subject. It is available for Case, KB Articles, Product Catalog items and Sales Literature.

We can customize Category Entity.

We can create forms, add fields, views, business rules, dashboards etc.

Can create 1 – N relationship from Category to other entities.

We cannot create N- 1 or N-N relationship.

It has N-N relationship with Knowledge Article entity

  • Is category User Owned or Organization Owned entity?

User Owned

  • How are they rendered inside form?

Subject are rendered as tree structure

Category are rendered as lookup

We can also specify Auto-numbering for Categories

  • What happens if a delete a Subject or category?

Deleting the subject will not delete its child record.

Deleting the category will delete its child record.

  • Can we run advanced find on Subject and Categories?

We can do it on Categories, not on Subject.

  • How does Subject render when used in advanced find filter condition? Tree view?

It renders like a lookup

Few considerations while migrating  Subject records

Hope it helps..