Microsoft Dynamics CRM – Nishant Rana's Weblog

Fix – Exception in creation of lead (Dynamics 365 Marketing)

We were getting this error in the submission of one of our outbound Marketing forms.

Activity id: e1ede147-efb6-457d-bc19-826c6176a2e4, Request id: jH7xRiEzGFTdZQTbE2fkh9_Z_WtjumCqJERuYZbGSL0_0, Exception: Entity ‘Contact’ With Id = 896b960d-c5d7-4c4d-95c7-a9e226afbf8e Does Not Exist

The form had only the Lead form matching defined and Only leads for Update contacts / leads.

So here because of some earlier multiple/different form submissions, a contact got created and stored in the browser’s cookie, which CRM was referring to, and trying to set a Parent Contact for the lead record even though we were having Only leads set for update contact/leads option.

This is the behavior of the product.

https://learn.microsoft.com/en-us/dynamics365/marketing/marketing-forms#createupdate-leads-only

The solution is to delete the cookie or try in incognito or in-private mode or a different browser, and it would work.

This would probably arise because while setting up marketing forms we would do multiple submissions with test data for testing.

Hope it helps..

Advertisements

Fixed – Expect non-empty Guid while importing solution in Dynamics 365/ Dataverse

While trying to import the solution (patch), we were getting the below error.

“Expected non-empty Guid”

There was hardly any detail in the log file also

We tried removing the solution component one by one in our source environment and trying the import again in the target environment.

Eventually removing the Pages (custom page) allowed us to import the solution successfully into the target environment.

We then compared the customization.xml of the current solution with the backup solution of the Target and see the information missing in the current solution.

Left is – Current solution (giving error) and Right is the backup solution of the target.

Interestingly next time when we extracted the new patch after a couple of days, we could see the tag there and so no issues that time.

Hope it helps.

Advertisements

How to – set Calendar View to start the week from Monday – Dynamics 365

By default, if the calendar view is starting on Sunday for the week as shown below, we can update the system settings, to start it on Monday or any other day

From Administration >> System Settings > > Formats >> Customize (Current Format)

Specify the First Day of Week

On update, we can see the view updated to show the week starting from Monday.

Hope it helps..

Advertisements

Fix – The label ‘ ‘, id: ” already exists. Supply unique labelid values while importing solution – Dynamics 365

Recently while trying to import the solution, we got the below error –

The tab tag was missing the labelid property. Adding it back to the FormXml using FormXml
Manager XrmToolBox plugin fixed it.

Also check – https://nishantrana.me/2022/11/11/adding-contact-insights-account-insights-to-the-form-dynamics-365-marketing/

Hope it helps..

Advertisements

Configure WhatsApp channel – Omnichannel (Dynamics 365)

To configure the WhatsApp channel, we need to set up the account in the Customer Service Admin Center.

Navigate to Customer Support >> Channels >> Messaging Accounts (Manage)

Select the New Account option there

Select WhatsApp as the channel

Next, we need Account SID and Authentication token.

To get this information we need to create a Twilio Account.

https://www.twilio.com/try-twilio

Navigate to the console and copy the Account ID and Authentication token

https://www.twilio.com/console

Enter Account SID and Authentication token click on Next

Next, we need to add the WhatsApp Name and Phone number

Navigate to Messaging >> Try it out >> Send a WhatsApp message to activate the WhatsApp Sandbox.

Follow the steps there to configure the Sandbox account. (scan the QR code send the Message, and test the Business and User-Initiated message/conversation).

Click on Sandbox setting tab to get more information

Copy the number.

Add the number and click on Next

Copy the URL

Paste that URL in the When a message comes in and save.

We can see our WhatsApp account created, open the record.

We can see our number being shown as Active

With the account active time to now it is time to set up the channel/workstream / queue.

Navigate to Customer Support >> Channels >> Messaging (Manage)

Click on Add Channel and add the details

Enter channel details

We are creating a new workstream

Add the WhatsApp number added

Select the language

Specify the Behaviour (automated messages and approved templates)

Specify the user features (attachments)

Review and Finish and Create the channel.

Open the workstream and specify routing rule/fallback queue/work distribution/associate bots etc details

We will create a ruleset to route the message to the queue

We have the below route-to-queue rule created to route to the default queue which has all the omnichannel agents added to it. (In an actual scenario, we would add the conditions and create a specific Advanced Queue).

We are leaving the rest of the settings/configuration as default.

Now is the time to test.

Let us log in to the Customer Service Workspace as an agent and from the registered sandbox participant number added send a message.

We are done with our configuration.

Get all the details

Hope it helps..

Advertisements

FaultException – RetrieveMultiple: GetEntityDataByFetchSearch while using Configuration Migration Tool – Dataverse / Dynamics 365

While recently trying to move configuration data using the Configuration Migration tool, we got the below error.

FaultException`1 - RetrieveMultiple : GetEntityDataByFetchSearch |=> 'msdyncrm_segment' entity doesn't contain attribute with Name = 'msdynmkt_name' and NameMapping = 'Logical'. MetadataCacheDetails: ProviderType=Dynamic, StandardCache=True, IsLoadedInStagedContext = False, Timestamp=65138568, MinActiveRowVersion=65138568, MetadataInstanceId=53062908, LastUpdated=2023-04-20 07:29:48.697, OrgId=f69f1cea-23d9-446f-9130-ed45ce666b28
Source : mscorlib
Method : HandleReturnMessage
Date : 21-04-2023
Time : 15:07:29
Error : Message: 'msdyncrm_segment' entity doesn't contain attribute with Name = 'msdynmkt_name' and NameMapping = 'Logical'. MetadataCacheDetails: ProviderType=Dynamic, StandardCache=True, IsLoadedInStagedContext = False, Timestamp=65138568, MinActiveRowVersion=65138568, MetadataInstanceId=53062908, LastUpdated=2023-04-20 07:29:48.697, OrgId=f69f1cea-23d9-446f-9130-ed45ce666b28

This was because we had the wrong filter condition applied to that table/entity.