Microsoft Dynamics CRM – Page 3 – Nishant Rana's Weblog

Fixed – Real-time marketing form’s Standalone page submitting to a different environment – (Dynamics 365 Customer Insights – Journeys)

Recently we migrated the Real-time marketing forms from our Dev environment to UAT environment using the Configuration Migration Tool. Here what we noticed was on submitting the form using the standalone page in UAT, the submissions were going back to the Dev environment instead of UAT.

A screenshot of a computer

Description automatically generated

This was because the data-form-api-url and data-cached-form-url property of msdynmkt_standalonehtml field of msdynmkt_marketingform record was still referencing the organization id of the Dev environment instead of UAT.

A computer screen shot of a computer screen

Description automatically generated

<div data-form-id='167fce01-b674-ef11-a671-002248e36298'
data-form-api-url='https://public-oce.mkt.dynamics.com/api/v1.0/orgs/f69f1cea-23d9-446f-9130-ed45ce666b28/landingpageforms'
data-cached-form-url='https://assets-oce.mkt.dynamics.com/f69f1cea-23d9-446f-9130-ed45ce666b28/digitalassets/forms/xxxfce01-b674-ef11-a671-002248e36298' ></div>

The f69f1cea-23d9-446f-9130-ed45ce666b28 is the development environment’s organization ID.

This information is stored in the msdynmkt_standalonehtml field of msdynmkt_marketingform record.

select msdynmkt_marketingformid,msdynmkt_standalonehtml,* from msdynmkt_marketingform where msdynmkt_marketingformid = ‘formGUID’

To fix we replaced the Dev’s Organization ID = f69f1cea-23d9-446f-9130-ed45ce666b28 with UAT’s Organization ID = dd628e4e-ffd7-ed11-aecf-002248932ace

<div data-form-id='167fce01-b674-ef11-a671-002248e36298'
data-form-api-url='https://public-oce.mkt.dynamics.com/api/v1.0/orgs/dd628e4e-ffd7-ed11-aecf-002248932ace/landingpageforms'
data-cached-form-url='https://assets-oce.mkt.dynamics.com/dd628e4e-ffd7-ed11-aecf-002248932ace/digitalassets/forms/xxxfce01-b674-ef11-a671-002248e36298' >

And updated the marketing form record.

Red text on a white background

Description automatically generated

update msdynmkt_marketingform
set msdynmkt_standalonehtml = '<div data-form-id=''067fce01-b674-ef11-a671-002248e36298''
 data-form-api-url=''https://public-oce.mkt.dynamics.com/api/v1.0/orgs/dd628e4e-ffd7-ed11-aecf-002248932ace/landingpageforms'' 
 data-cached-form-url=''https://assets-oce.mkt.dynamics.com/dd628e4e-ffd7-ed11-aecf-002248932ace/digitalassets/forms/067fce01-b674-ef11-a671-002248e36298'' >
 </div><script src = ''https://cxppusa1formui01cdnsa01-endpoint.azureedge.net/oce/FormLoader/FormLoader.bundle.js''></script>'
where msdynmkt_marketingformid = '067fce01-b674-ef11-a671-002248e36298'

After the update we can see submission reflecting back to the correct UAT environment.

The query we used to update all the forms with UAT’s Id

-- replace Dev Org ID with UAT Org ID in all the marketing forms 
UPDATE msdynmkt_marketingform
SET msdynmkt_standalonehtml = REPLACE(msdynmkt_standalonehtml, 'f69f1cea-23d9-446f-9130-ed45ce666b28', 'dd628e4e-ffd7-ed11-aecf-002248932ace')
where msdynmkt_standalonehtml is not null

Hope it helps..

Advertisements

How to deal with the Calculated columns having Null values (Dynamics 365 / Dataverse)

Suppose we have the following whole number fields, where Field C is the calculated column and is the sum of Field A and Field B

A screenshot of a contact form

Description automatically generated

Field C calculated column –

However, if any of the fields used for calculation is null, Field C will also show null.

The way we can resolve it is to put a null check in the formula.

We have created a new calculated column with the below definition.

The other option that we can consider is using JavaScript / Business Rules / Additional Calculated Columns to set the default value to 0 in case of null, for the fields being used for calculation.

In the case of 0 also, the calculated columns will work properly.

Finally, now that we have Fx Formula Columns available we can make use of them instead of Calculated Columns.

The formula columns work properly and we do not have to put the null check.

Get more details on Fx Formula Columns

Hope it helps..

Advertisements

Using Microsoft Copilot Studio to create Copilot for Teams channel with Dataverse as Knowledge source – Copilot / Dataverse

Below are the quick steps to create a copilot with Dataverse as the Knowledge source and Teams as the channel

Open the Microsoft Copilot Studio site https://www.microsoft.com/en-us/microsoft-copilot/microsoft-copilot-studio

Select the Try free option to get started.

Select the appropriate environment and click on New copilot option (Create+)

Select Create

Here we have renamed the Copilot, next click on Add knowledge to add Dataverse as the source.

Add Dataverse

We can select up to 15 tables, and we have specified lead, contact, account, and case for now.

Next, we get the option to review the data for the tables selected.

In the last step, we get the option to review it. Here we can add/ edit the synonyms and glossaries that would make it easier for the copilot to understand and fetch the data. We’d skip it just to see how it works without configuring them.

Our copilot is ready now. The other things that we can do are to add actions, build topics, and publish which we’d leave as it is for now.

Click on the Knowledge tab. In a short time, we’d see the status changed to In Progress

Meanwhile, we can still go ahead and test it.

A screenshot of a chat

Description automatically generated

As we are done with the testing let us try publishing it, before that let us check the authentication for it.

Navigate to Settings >> Security >> Authentication, here we can see Authenticate with Microsoft selected. We’d leave it like that.

Based on the Authentication mode selected, we will have different channels enabled / disabled.

Let us select the Microsoft Teams channel for our copilot.

Select Turn on Teams

Select Edit details

Add / Edit the details and click on Save.

Now time to Publish our copilot.

We can now again open the Microsoft Teams channel and select the Availability options.

Here we can see multiple options, one is to share the link, upload the zip, and show it in the teams store.

We selected the Show to my teammates and shared users option. We can add search and add users to share it with them.

The other option is to Copy link and share the link.

On opening the link, we get the option to add the app.

We can see our app added in the Manage your apps section in Teams.

Finally now we can start interacting with our copilot.

Get all the details –

https://learn.microsoft.com/en-us/microsoft-copilot-studio/

Hope it helps..

How to remove contact and customer validation on Cases– Dynamics 365

By default, we can only specify the contact associated with the customer for the case record. If we try specifying a contact record that is not associated with the Customer selected, we will get the below error message.

Invalid Contact – The specified contact doesn’t belong to the account selected as the customer. Specify a contact that belongs to the selected account, and then try again.

Also, CRM will filter the lookup to show only the associated contact record

However, if we do not want this validation, we can remove it using the environment variable.

Search for Customer Entities Relationship For Incidents / msdyn_IncidentShouldValidatePrimaryContact

Set the new value as 0.

Now we will be able to save the record using an unassociated contact.

A screenshot of a test case

Description automatically generated

Get all the details here

Hope it helps..

Use OptionSet Wrapper component to show color-coded options on the form – Model-driven apps/ Dynamics 365

We can make use of the OptionSet Wrapper component to show color-coded options on the form for the choices or option set fields.

Below we have added the Option Set wrapper component to the Rating field of the lead in the Lead (Main) form.

We can see the field added but do not see any colors for it.

This is because it uses the color defined for that column, which wasn’t defined out of the box for that field.

We then defined the colors as shown below for different choices / options.

After saving and publishing our changes, we were able to see the corresponding color for the choices.

Also check –

Due Open Activities Control – https://nishantrana.me/2023/05/09/due-open-activities-control-dynamics-365/
Notes Control – https://nishantrana.me/2023/05/10/notes-control-dynamics-365/
Attachment Control – https://nishantrana.me/2023/05/08/new-attachment-control-dynamics-365/

Hope it helps..

Advertisements

New Lead Qualification Experience – Dynamics 365 Sales

To enable the new lead experience, navigate to App Settings >> Lead + opportunity management in the Sales Hub App.

On enabling it, we get the option to specify whether the Account, Contact, and Opportunity records are created automatically or the user (seller) has the option to specify which record to create.

We also see the option to Copilot summarizing the case once a lead is qualified.

For opportunity, if we select Seller, we get an additional option to modify the Opportunity form by adding or removing fields and also the option to allow a maximum of 5 new opportunities during lead qualification.

Clicking on the Add or remove fields link opens the Opportunity qualify lead form for customization.

Let us see it in action.

On clicking the Qualify command, we can see the new Qualify lead dialog opened in the side pane.

It gives us the option to create a new Account, Contact, and/or Opportunity record.

For Account and Contact, we can specify an existing record or select none if we do not want the Account and Contact record to be created.

For opportunity, we can click on edit icon to update the details of the opportunity record to be created. It will open the Opportunity qualify lead form.