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..
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..
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.
Updating the filter to use correct attribute fixed the issue.
Hope it helps..
To enable the new email address validation feature (preview), log in to Power Platform Admin Center >> Settings >> Features >> Data Validation
Switch On – Data Validation. (Interestingly in one of the environments enabling this setting was enough to get the smart email validation working however in another environment had to enable the below settings as well to get that working)
Next open the Model Driven App in Maker Portal – App Designer and switch on Enable Smart Email Address Validation Control
Below we can see it validating the email address while we enter its value
We get the below messages
And this works for the email field in a custom entity as well.
Refer – https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-validation-email-column
Also, check the similar feature we have for Sales Hub App
Hope it helps..
Recently we were getting the below error in one of our marketing forms for form submission record.
Exception in Creation of lead – Activity id: 40ff82fc-bb10-4d30-8671-12683392ccdf, Request id: AsChkx2zn5IKrjHVC4cTb6j-ZkB23D0PqgCdxwi8kEE_0, Exception: An item with the same key has already been added.
This was because we had mistakenly added first name fields twice as the form-matching attribute in the form-matching rule used for that form.
Deleting that extra field resolved the issue for us.
Hope it helps..
Security roles can be now managed using the new modern UI (preview).
Select Security Roles (See all) for an environment, within Power Platform Admin Center.
Select Edit for a security role.
We can see here Display only parent security roles option is On by default.
We can see the different options.
2. Specify Member’s privilege inheritance option
Nicely explained here –
3. Tabs for Table specific, Miscellaneous, and Privacy-related privileges
4. Filter privileges further by all, assigned or unassigned.
5. Collapsible
6. Option to Copy Table Permission to another table(s) and apply predefined Permission Settings i.e. Access Levels.
Copy table permissions to multiple tables
Permission Settings (Access Levels)
7. Specify Access Level for Privileges
Get all the details here – Security Roles and new modern UI
Hope it helps..
Nishant Rana's Weblog 