CRM – Page 57 – Nishant Rana's Weblog

Configure Case Topic Analysis using Cognitive Services Text Analytics (Preview) in Dynamics 365 (online)

“Update – The Cognitive Services Text Analytics Topic Detection API required for this feature will be removed as of August 24, which means this feature will no longer work after that date and a topic analysis run will return an error.”

https://technet.microsoft.com/en-us/library/mt752501.aspx

Text Analytics Preview feature is currently available for instances in US region. Topic analysis can be used to automatically identify topics that occurs in cases.

To enable the preview, go to System Settings – Preview tab and select Yes for Text Analytics Preview.

Click OK to confirm.

Next go to Administration and click on Azure Machine Learning Text Analytics Service configuration to configure the service.

Here we would need the Azure service URL and the Azure Account Key to configure it.

To do so, go to Azure Portal

https://portal.azure.com

Search for Cognitive Service Accounts

Click on Add and Specify required information.

Select Text Analytics API as API Type.

Click on create to create the service account.

Copy the Endpoint of the created Cognitive service account which will be used as Azure Service URL in CRM.

Similarly select Keys, and copy one of the Key which will be used as Azure Service Key in CRM.

Specify the values in the Text Analytics Connection record.

Click on Test Connection to test the connection.

After successful test, click on Activate to activate the connection.

Next let us create a Topic Model which will be used to identify topics occurring in the cases.

Go to Service Management – Automatic Case Topics Analysis Settings

Create a new Topic model record

Create a related Topic Model Configuration record.

It auto populates the Topic Determination Fields which we can edit\add.

Specify the configuration record created in the Configuration lookup of Topic model record.

Click on Test to the configuration.

Build Execution History tab shows the status of the test run.

The build can be scheduled.

Once we have tested the configuration we can then activate the model.

Once Activated, we can them manually trigger the build using Build button

We can check the status of the build in the build execution history tab. Below record shows the build to be succeeded, duration it took i.e. 6 minutes, number of records it synchronized i.e. 159 and topics identified as 9.

To see it in action, go to Active Cases view and select Case Topics chart which lists the topics.

Hope it helps..

Configure Dynamics 365 and Azure Service Bus Integration (using TwoWay relay, Azure Aware Plugin and listener)

Let us pick up from where we left in the previous post and implement two way relaying through which we can get the response back from the listener.

https://nishantrana.me/2017/03/22/configure-dynamics-365-and-azure-service-bus-integration-using-oneway-relay-and-listener/

First let us update the Service Endpoint Registration, change the designation type to TwoWay, it would also ask to enter the SAS Key. Copy it from Azure and paste it.

Update the listener windows application created in the previous post to implement ITwoWayServiceEndpointPlugin

Use the below code to create the custom azure aware plugin.

Get the service endpoint id from the Properties window of the Service End Point registered.

As we are using trace service to log the response, set All for Enable logging to plugin-trace log option from Administration – System Setting – Customization.

Start the listener windows application and to trigger the plugin, create the lead record

We can see the execute method being called from Azure Service bus on create of Lead record.

The message being returned from listener application to the plugin.

The newly created lead record.

The trace message within the plugin –

Plugin Trace log with the response received from the listener –

Hope it helps..

How to -Configure Data Export Service in Microsoft Dynamics 365

*Updated 19 Sep – 2018 : Check out this powerful tool DBSync’s CRM connector, which could be used for bi-directional seamless integration of all the popular Application and Database with Microsoft Dynamcis 365- https://www.mydbsync.com/product/microsoft-dynamics-365-crm-integration

Data Export Service is an add-on that allows replicating CRM Online Data to Azure SQL Database.

The below video by expert Scott Durow is the best resource to learn about it

https://www.youtube.com/watch?v=txms2Yvn6Vc

Below are the steps we need to follow to configure it.

Go to Settings – Dynamics Marketplace

Search for Dynamics 365 Export Service

Click on GET IT NOW

Click on Agree

This will install the Data Export Service solution

Back in CRM – Go to Settings – Data Export. (Pop up window will open up a page for Data Export Authentication, so we need to enable pop up)

Click on New to create a new Data Export File.

Basically, here we need the Key Vault URL here which stores the database connection string securely.

Clicking on the information icon opens up the dialog box with the below PowerShell script, which needs value for variables like subscription id, key vault name, secret name, tenant id etc.

i.e.

So as a first step here we need to configure Azure Active Directory (if Office 365 and Azure Tenant are separate)

https://docs.microsoft.com/en-us/azure/billing/billing-add-office-365-tenant-to-azure-subscription

Next step is to create Azure SQL database. Search for SQL databases in All Resources and click on Add

Specify the required information and click Create.

Next we need to create a User that will be used to configure Data Export Service and has appropriate rights in the database

Here the user has been assigned db owner role

For the minimum rights required check the below article

https://technet.microsoft.com/en-us/library/mt744592.aspx

Now let us replace the below placeholders one by one

Subscription ID –
Key Vault Name – NishantDemoKeyVault
Secret Name – DataExport
Resource Group – DemoRG
Location – East US
Connection String –

Organization ID List –

Tenant Id –

https://login.windows.net/8e6d9cc0-cd4d-472e-98ab-088b1a6a1233/federationmetadata/2007-06/federationmetadata.xml
Get the GUID part – 8e6d9cc0-cd4d-472e-98ab-088b1a6a1233
Now let us run the PowerShell Script and copy the Connection Key Vault
URL

KeyVault record created in Azure à

Going back to our Export Profile wizard, we need to paste the Key Vault URL

Click on Validate

Select the entity or entities for which profile needs to be created

Select any relationships

Next click on Create and Activate

This creates the profile record in CRM

Once Initial Sync Status shows as completed we can see the tables created in the Azure Database.

The records synchronized –

Let us delete the below selected lead records –

Delete Log table will hold the information of the deleted lead records

To create export profile for a custom entity, (say for e.g. entity named Test in our case)

We need to enable Change Tracking in it.

Get all the details here

http://develop1.net/public/post/Dynamic365-Data-Export-Service.aspx

https://technet.microsoft.com/library/a70feedc-12b9-4a2d-baf0-f489cdcc177d

Hope this helps..

Create a simple logic app with Dynamics 365 connector

Let us create a simple logic app that on create of a contact record in CRM creates the same contact in Gmail.

https://portal.azure.com/#create/hub

Select New Logic App

Specify Name, Resource Group and Location for the logic app.

Select Blank Logic App

Select “When a record is created” as Trigger.

Select the Organization name and Entity as Contact.

Select Add an action and the New Step

Choose Google Contacts as the Service

Allow permission to Logic App to access Gmail

Configure Full Name and Primary Email (Dynamic content) as the values for the contact record to be created in Gmail.

Save and Run the app.

Create the new contact record in CRM that triggers the logic app.

On Successful run à

We can see the contact record created in Gmail.

Find all the details here

https://docs.microsoft.com/en-us/azure/connectors/connectors-create-api-crmonline

Hope it helps..

Partner Field Service Portal in Dynamics 365.

Dynamics 365 comes with Partner Field Service portal which helps Partners manage work order, service request, assets, invoices, opportunities etc. from within the portal.

Go to Administrator Center, select Portal and click on Manage.

Select Manage Dynamics 365 Instance

Click on Update Dynamics 365 Instance

Select Partner as Audience and Partner Field Service as the portal to be deployed

Once installed this is how Partner Portal looks like

Below are the different menu options that comes OOB.

Partner Program

Opportunities

Customers

Field Service

Below are the Entity Forms associated to the Partner Portal Web site created in CRM.

Below are the Entity Lists associated to the Partner Portal Web site created in CRM.

Around 121 Entity Permission records are added by the Partner Portal

Web Roles specific to Partner Portal.

Below are some of the permission for the Partner Admin web role.

Once the portal is setup next step would be to Become a Partner. Click on Begin Here.

Update the profile and click on submit.

Within CRM, the admin user needs to run the Approve Partner Application workflow on the corresponding portal contact user record.

After workflow succeeds we can assign appropriate web roles to the portal contact user.

The portal user can create customer contacts record

The portal user can raise Service Requests from within the portal.

Can manage Work Orders.

Can manage Opportunities.

The portal has the Dashboard that shows the details around the opportunity and the cases.

Hope it helps..

How to – Edit Primary Navigation in Portal in Dynamics 365

For updating the Navigation, login to the portal with the user having Administrator web role.

Hover over the Navigation and select Edit

This opens up the dialog box, here we can edit or insert a new navigation link. To add new navigation link click on “+”

We can either specify any existing page within portal or can point to any external URL and can also show up image + text or image only.

This adds the new navigation link

Similarly, we can add new child links or move a link as child link which then appears as drop down. Here we have moved the new Search Home link inside Support by dragging.