Dynamics 365 – Page 23 – Nishant Rana's Weblog

Use RetrieveDuplicates request to check for duplicates before creating/updating a record – Dataverse / Dynamics 365

In the previous post, we saw how we can use the SuppressDuplicateDetection parameter to throw errors in case of duplicates when creating or updating a record.

Here instead of relying on exception, we can make use of the RetrieveDuplicatesRequest message to detect the duplicates.

Let us take the “Leads with the same e-mail address” duplicate detection rule to see it in action.

We can see 3 lead records already existing in the system with the same email address.

Below is our code that is trying to create a new lead record with the same email address and using the RetrieveDuplicatesRequest to check for the duplicates.

Below we can see that not only do we get the total number of duplicates found, but we can also get the details of the duplicate records found.

Get all the details here.

Hope it helps..

Advertisements

Use SuppressDuplicateDetection parameter of Request to throw an exception in case of duplicates – Dataverse / Dynamics 365

We can make use SuppressDuplicateDetection optional parameter of the Request if we want the configured duplicate detection rules to run and throw an exception while creating or updating the record.

We will use the below out-of-the-box duplicate detection rule, that checks for lead having same email address.

Below is our code and we can see the lead records with the same email address getting created without any exception.

Now we have updated the code to use the SuppressDuplicateDetection optional parameter. We have set it as false.

As expected this time we get the exception.

“The record was not created or updated because a duplicate of the current record already exists.”

Hope it helps..

Advertisements

How to – Connect Dynamics 365 records and views to Microsoft Team channels – Dynamics 365

To enable the feature that allows linking existing Dynamics 365 records and views to a Team channel,

we need select the environment and navigate to Settings >> Team Integration Settings

Select Yes for the “Turn on the linking of Dynamics 365 records to Microsoft Teams channels” and save it.

Now back in Microsoft Teams, from a team channel, select the Add (+) option

Select Dynamics 365

Specify the environment, and the corresponding Dynamcis 365 Apps in it.

Check Rememer this preference and click on Select.

Next, we get the option to search and filter for a record to link to.

Here we have selected the contact Nancy Anderson record, click on Save.

We can see the selected contact record pinned.

We also get the below options for the record tab added.

Similarly, if we want to link to a view, we can select the table and then its corresponding view to select and click on Save.

We can see the selected view added.

Also for both records and views pinned, we get the option of starting the conversation.

Clicking in Start conversation adds the below message with the link to the tab where the view or the record has been added or linked.

Get all the details here

Hope it helps..

Advertisements

How to – convert basic queue to an advanced queue – Dynamics 365

We can convert our basic queue to an advanced queue by setting the field “Is Omnichannel Queue” or “Automatic work distribution” schema name “msdyn_isomnichannelqueue“- to Yes.

We would usually do it to use the existing basic queue in the Unified Routing.

We can find that option in the Conflicts Tab of the Queue form

Or in case you cannot find the conflicts tab, you can add the field to the form

Here we need to be careful while converting the basic queue to an advanced queue, as we cannot revert this. If we try to do this we will get the below error –

Get more details here.

Hope it helps..

Advertisements

How to – enable the enhanced email template editor in Model-driven Apps(Dynamics 365 / Dataverse)

Below is what our existing or current Email Template editor looks like (Sales Hub >> Personal Settings >> Email templates)

Let us now enable the Enhanced Email Template editor for the App / Environment (it is enabled by default for Customer Service workspace and Customer Service Hub apps)

Create or Open an existing solution, Add existing >> Setting >> Enable the New Email Template Editor

We can set the value as Yes for the Setting environment value to apply it for the environment.

To enable it for a specific app, make sure we have the option “Environment and apps” and “Apps Only” selected for Value can be changed for option.

To specify the app(s) for which we want to enable the new email template editor, we need to add that corresponding app to the solution.

Here we have added the Sales Hub.

Add Existing >> App >> Model-driven App >> Sales Hub

On adding the Sales Hub App, we get the option to set the value for the Sales Hub app, which we have set as Yes.

Publish all customization.

We can now see the new Editor tab added for the new Email Template record inside Sales Hub.

We can drag and drop, and specify properties, of the layout section and elements in the new editor.

The new email template editor uses the same design as the email editor in Dynamics 365 Marketing, making it more consistent across the different apps in the platform.

Get all the details here.

Hope it helps..

Advertisements

Link and Create a case, contact, and account from a notes record in Timeline– Dynamics 365 / Dataverse

From the notes in the timeline, now we can link an existing note to an existing case, contact, or account record (this will unlink it from the current record) and also create either a new case, contact, or account record.

To configure it, open the Notes property of the Timeline section in the form.

Below we can see the different properties we can configure.

Enable the Link to Table Command
Enable the Tables to be connected.

Here we are enabling the Contact table, and then specfiying the Quick Create Form to be used while creating the new contact record, and also the mapping of the title and description field of the Notes. We have the same configuration for Case and Account.