Dynamics 365 – Page 49 – Nishant Rana's Weblog

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

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 –

CRUD, Export to Excel, SDK Calls.
CRUM and backend activities performed by the support engineer.
Report – viewed, exported, multimedia assets shown in the Report

For this first Auditing needs to be enabled in the environment.

Navigate to Settings > Administration > System Settings > Auditing Tab

Navigate to Compliance Center

https://protection.office.com/

Search > Audit Search Log and
Turn on auditing.

To try the new experience within the Compliance center

https://compliance.microsoft.com/auditlogsearch?viewid=Search

After around 1 hour or so, the settings got enabled.

As specified Office 365 logs are being prepared, if we try searching we’d get blank results

Below are the list of Dynamics 365 and Power Apps activities that can be tracked

Around after 3 hours or so – we saw the results appearing.

Export has 2 options –

Save loaded results –

Download all results –

At the same time there we 51 records in Audit Summary View.

Apart from searching for an audit log, we can also define an audit retention policy as shown below

Get the sample files here –

https://drive.google.com/file/d/1akifraP1NCV-KgmA-8ROhm8r4h0tAcLi/view?usp=sharing

https://drive.google.com/file/d/1s_EbJ4hraDl6YEVUCMkOe6bQbXCJu_5-/view?usp=sharing

Get all the details here

https://docs.microsoft.com/en-gb/microsoft-365/compliance/search-the-audit-log-in-security-and-compliance?view=o365-worldwide

Hope it helps..

Advertisements

Check access to a record in Dynamics 365

Using the Check Box button in the command bar, the user can now check the privileges he has on the record.

It also provides the details on how he has that particular privileges on the record, either through Security Roles assigned directly or through the team user is part of or through the Hierarchy security.

To see it in action, open a record and select Check Access

E.g. the below user has Read, Write, Create, Delete, Append, Append To, Assign, Share rights on the contact record, assigned directly as he has the system administrator role.