Nishant Rana

Macros in Omnichannel and Customer Service Workspace – Dynamics 365

Macros enables users to perform the set of sequential actions – repetitive and monotonous – in a more process compliant manner, which can be reused across different sessions, making it faster, more efficient and less error prone.

To define a Macro, navigate to Omnichannel Administration app > Agent Experience > Macros

Posts on Omnichannel for Customer Service (Dynamics 365)

The interface is similar to Power Automate with some predefined automation actions.

Session Connector has the following actions >

Omnichannel Connector has the following actions >

Flow Connector has the following actions >

Productivity Automation has the following actions >

Get all the details here –https://docs.microsoft.com/en-us/dynamics365/app-profile-manager/macros

Now back to our Macro, select Productivity Automation trigger.

Select the action Start macro execution.

Select Clone current record.

Specify the title of the cloned record.

Let us create a new Agent Script with Agent Script step having Action Type as Macro.

Agent Script – https://nishantrana.me/2021/03/02/agent-scripts-in-omnichannel-and-customer-service-workspace-dynamics-365/

Navigate to Omnichannel Administration > Agent Experience > Agent Script and create a new Agent Script.

Follow it by adding a new Agent script step.

Below is our Agent script step record

which is associated with the Agent Script record

Now to test it let us open an existing record within a new session (Shift + record click) within Customer Service Workspace.

More on Customer Service Workspace –https://nishantrana.me/2020/08/13/new-customer-service-workspace-app-preview-in-dynamics-365-2020-release-wave-2/

Select Clone Record for the record to be opened in the new session.

As expected selecting on Clone Record – opens the clone of the record in a new Tab as shown below

We can also check the run history of the Macro using View run history option

That was a very basic example we saw, now with the option of running flow i.e. Run Flow as Macro using the Flow Connector, the possibility is limitless.

Hope it helps..

Advertisements

Fixed – Error – “Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server” – while trying to use Dataverse connector in Power BI

While trying to use Dataverse connector inside Power BI Desktop

we got the below error

Details: “Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)”

Later we realized we were not entering the environment details in the correct format as expected

i.e.

[orgname].[crm].dynamics.com

We were entering it incorrectly below with the https

Entering URL in correct format fixed the issue for us.

In case if TDS endpoint it not enabled –

we will get the below error

i.e. Microsoft SQL: TDS Protocol endpoint is disabled for this organization.

Check more posts on Power BI

https://nishantrana.me/category/power-bi/

Hope it helps..

Advertisements

Agent scripts in Omnichannel and Customer Service Workspace – Dynamics 365

Agent scripts are available within the Productivity pane in the Customer Service workspace and Omnichannel for the Customer Service app.

Agent scripts contains series of steps that will guide the agents while working, helping them to be more efficient.

More on Customer Service Workspace – https://nishantrana.me/2020/08/13/new-customer-service-workspace-app-preview-in-dynamics-365-2020-release-wave-2/

Omnichannel for Customer Service –https://nishantrana.me/category/omnichannel/

Smart Assist –https://nishantrana.me/2020/08/17/ai-suggestions-for-similar-knowledge-articles-and-cases-in-dynamics-365-2020-release-2020-wave-2/

To define Agent Scripts – navigate to Customer Service Hub > Service Management > Agent Scripts or Omnichannel Administration > Agent Experience > Agent Scripts

Create a new Agent script record, and specify steps for the same by creating new agent script step record.

We can define 3 different types of Action – Text, Macro, and Script.

For simplicity, we have selected Text here.

We have defined 2 script steps for the agent script as shown below.

Next, we need to associate the Agent Script with the Session template.

Inside the Omnichannel Administration > Agent Experience > Sessions, select the template we want the script to be associated.

Here let us select the Case entity session – default template

We can also define the conditions for the default agent script to be applied using the Enable Build expression option.

https://docs.microsoft.com/en-us/dynamics365/app-profile-manager/agent-scripts#set-the-default-agent-script-for-agents

For now to make the example simple, we leave it as No (default).

Back in Customer Service Workspace or Omnichannel for Customer Service App– Shift + click the case record to open the new session in the Active Cases grid.

We can see the script populated there for the agent on the case record opened.

If we have multiple scripts associated with the Session template – the agent has the option to select the appropriate script.

Hope it helps..

Advertisements

Do you use FetchXML Builder? Please consider helping a friend out.

Dynamics 365 community rallies around Microsoft MVP and FetchXML Builder creator Jonas Rapp

https://msdynamicsworld.com/story/dynamics-365-community-rallies-around-microsoft-mvp-and-fetchxml-builder-creator-jonas-rapp

https://fetchxmlbuilder.com/donate

The ReadyXRM Blog by Nick Doelman

I use the FetchXML Builder on my Power Platform almost on a daily basis. It saves me so much in building SSRS reports, it allows me to build powerful Power Apps portals web templates and it also helps me building Power Automate flow queries.

What is FetchXML Builder? It is a tool that is part of the XrmToolBox that allows you to quickly point and click choose tables from Dataverse (aka entities from Common Data Service/Dynamics CRM), choose the columns, filtering, sorting, etc and it will generate equivalent FetchXML, OData, JSON formats, etc.

The tool has saved me personally 100s of hours… and world wide I am sure it has saved customers, partners, consultants, developers *millions* of hours… considering standard billable rates, the cost savings are enough to fund research into life saving treatments many times over or to feed thousands of children in developing nations.

Why do I mention…

View original post 218 more words

Activity Logging – Dynamics 365 Apps

Microsoft 365 Security and Compliance Center – provides easy access to the data and the tools to manage the compliance need of an organization, and also can be used to review the different data processing activities within Dynamics 365 Customer Engagement apps.

It required Microsoft 365 E3 or E5 subscription and is only available for Production environments.

The events logged are –