CRM – Page 5 – Nishant Rana's Weblog

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

Fixed – Plug-in assembly fullnames must be unique (ignoring the version build and revision number) – Dynamics 365 / Dataverse

Recently while trying to register the plugin, we got the below error

Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). —> Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number).

It was because we were trying to register the assembly which was already registered in that environment, instead of updating it.

Also, refer – https://helpfulbit.com/plugin-assemby-fullnames-must-be-unique/

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.

Save and publish the changes.

We can now see the option to Link to record for the notes.

We get the option to search for an existing record (it will show results from tables connected).

Clicking on Advanced opens the lookup dialog.

On Associating to an existing record, the notes get linked to the new record and unlinked to the current record.

We can see the notes record associated with the contact record and removed from the existing case record.

We can also use the plus + sign to create new records of the tables connected from the notes.

Account, Case, and Contact in this case.

This opens the Quick Create form, with the title and description field of the notes mapped.

After the new record gets created, we are again presented with the option to Unlink that existing note from the current record.

Below we can see the new record with the note associated with it.

Get all the details here

Hope it helps..

Advertisements

Entity Id must be specified for Operation – Dataverse / Dynamics 365

We might get the below error while performing the update operation.

This could be if we have not specified the GUID of the record to be updated or if we are using an Alternate Key to update the record, we have not specified the KeyAttributes property.

We either need to specify the Id property or specify the KeyAttributes property

Or in the Entity’s Constructor.

Hope it helps..

Advertisements

ERROR REQUESTING Token FROM THE Authentication context – General ADAL Error (Dataverse / Dynamics 365)

We might get the below error while connecting to the Dataverse Web API using the client ID and client secret.

AADSTS700016: Application with identifier ‘6d8ff73a-27ef-443c-b524-d8b69ae87580’ was not found in the directory ‘w72tk’. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

This could be if we have specified wrong Client or App Id.

Check the correct App Id either from Azure you can also refer to the correponding Application User created for it.

Hope it helps..

Advertisements

Use Copilot to create a journey – Dynamics 365 Marketing

We can make use of Copilot to create a journey for us, using everyday conversational language.

To enable it, navigate to

Settings >> Overview >> Feature Switches >> Journey (Copilot)

Let us see it in action, by creating a new journey record.

We get the option to select predefined
examples to start with.

Here we have selected the last example “When a contact submits a marketing form, assign a phone call….”

On selecting it, we are presented with the option to specify the Trigger.

We have selected the existing Marketing Form Submitted trigger record here.

After specifying the trigger, we get the option to specify the marketing form or to leave it empty to run it for all the form submissions and also the audience type, which could be either Contact or Lead.