Nishant Rana

Omnichannel Real-time analytics reports (Preview) – Dynamics 365 Customer Service

The Real-time dashboard consists Summary, Ongoing conversation, Agent, and Voice report.

To enable it – Login into Customer Service Admin Center >> Operations >> Insights >> Report Settings >> Real-time Analytics (preview)

Enable it –

After a couple of minutes, we can see the Dashboard added to the Customer Service Workspace app.

Within the Summary, we can get the details of any ongoing conversation, KPIs, etc.

The ongoing conversation report shows the details of all the ongoing conversations

The agent shows all the real-time details about the agents

We can select an agent from Agent List and click on Details to show additional details about the agent.

Finally, the Voice report shows details specific to Voice Channel / Queues.

Get all the details here – Real-time analytics dashboards (preview)

Hope it helps..

Advertisements

New look-and-feel model-driven apps: A comparison and my thoughts

Power⚡Thomas

It was already announced in the Power Platform 2023 Release Wave 1 and since last Thursday, February 2, 2023, it has become available in preview. I am referring to the new look-and-feel for Model-driven Apps.

Last year, I already posted a LinkedIn post in which I discovered that there had been an improvement in the UI of Model-driven Apps. This turned out to be part of the 2022 Release Wave 2.

The design is based on Microsoft’s Fluent UI Framework, which is also used in office applications such as Outlook, Word, Excel, and PowerPoint. However, this improvement goes a step further than what was announced last year. This time, elements such as controls, command bar, header, navigation, and grid views have also been tackled. In this blog post, I will make a comparison for each element and share my thoughts on it.

View original post 1,045 more words

Contact’s Originating Lead – originatingleadid is not valid for update – Dynamics 365 / Dataverse

Recently we were writing a plugin that on the creation of a lead updates the originating lead of a contact record. The value was neither getting updated nor we were getting any errors.It was after we spent a good amount of time debugging, realized that this field cannot be updated.So basically, we can specify a value for it during create of contact but cannot update it.

Hope it helps..

Advertisements

How to – Identify Dynamics 365 Marketing Application App and its corresponding environment

We can easily identify the Marketing App and the environment in which it has been provisioned.

https://admin.powerplatform.microsoft.com/

We can find the unique name of the environment/organization suffixed with the name of the app i.e. Dynamics 365 Marketing Application for the configured app.

Navigate to the environment’s Advanced Settings >> Customizations >> Developer Resources

We can find the Unique Name of our organization there

Hope it helps..

Advertisements

Handle HTTP request failures in Power Automate

Mohamed Ashiq Faleel

If the HTTP request you make in Power Automate cloud flow gets a 200 OK response, all is good but if the HTTP response has the status codes like 408 – Request Timeout, 429 – Too many requests, 522 – Connection Timeout, 404 – Not found, 400 – Bad request etc there is a problem which needs attention. This post will show you how to handle HTTP request failures using

Retry Policy
Custom Retry for requests which cannot be handled by Retry Policy
Take actions based on HTTP status code

Retry Policy:

A Retry Policy specifies how the action or trigger retries a request when the original request times out or fails. The retry policy handles the following HTTP status codes

408 – Request Timeout
429 – Too many requests
5xx – xx refers to any number like 500 – Internal server error, 503 – Service Unavailable, 522 – Connection…

View original post 839 more words

Moving Marketing Email, Journey, Events, etc. between environments – Dynamics 365 Marketing

To move Marketing configurations/data from one environment to another we can make use of the Configuration Migration Tool.

Open the tool, and create the schema file. Connect to the source environment.

Select and add the real-time marketing email table – msdynmkt_email Soure email.

Next, we are going to select the real-time marketing Journey table – msdynmkt_journey

Source Journey.

Lastly events – msevtmgt_event

Source events.

Click on Save and Export –

Save the schema file and click on yes.

Click on Export data to generate the data to be exported.

Next with the schema and data exported, select Import Data to start the import and select destination organization.

Select the data file exported earlier and start the import process.

The import process gets completed with a warning for the table Event for one of the records.

Let us now check the destination environment.

We can see 4 Email records created and 1 updated, all in Draft Status.

We can see all 4 journey records created.

And 2 event records were created.

In case we want to filter the records or want to make sure records are not updated in the destination, we can select Tools >> Configure Import Settings