Recently while trying to use the new CreateMutipleRequest message we got the below error –
“The ‘CreateMultiple’ method does not support entities of type ‘none’. MessageProcessorCache returned MessageProcessor.Empty”
It was because we were not populating the EntityName property of EntityCollection class. Specifying it fixed the issue.
Hope it helps..
For part 1 –
Recently we were getting the below issue for our Marketing Forms hosted on an external website on a particular authenticated domain. The pages were working fine in other authenticated domains.
“The domain where this form is embedded might not be enlisted as a domain record for externally hosted forms. Otherwise, a browser extension or plugin may be blocking this form from loading. Review and reload form to continue.”
This particular domain was also shown as authenticated in our Dynamics 365 marketing.
Our website was e.g. https://www.domain.kiwi/ so we had domain.kiwi authenticated in Dynamics 365 Marketing.
Eventually, we had to raise a Microsoft Support Ticket and were instructed to add/ authenticate www.domain.kiwi (with www.) also, doing so resolved the issue for us.
Also, there seemed like a UI bug in the Marketing which will cut out “www.” automatically when trying to authenticate the domains.
Hope it helps..
To set up the Omnichannel –
To setup Facebook Channel,
Login to https://developers.facebook.com/, create a new account or use an existing developer account
Create a new Facebook App
Select the app type as Business
Provide an appropriate name and create the app.
Select Messenger as the Product for the app.
Next either add an existing page or create a new one and then add the newly created page in the Messenger >> Settings
Here we created a new page and have added that page.
We can also Generate token for the page, which we will use while configuring Facebook Channel in Dynamics 365.
Click on Generate token and copy the token. Also, save the Page Id below the name of the page.
We will also need App ID and App Secret, which we can get from – Settings >> Basic
Next, we add a few test accounts to the app for testing/using the app. (we are not making the app publicly available or live, which would require and approval process)
Navigate to App Roles >> Roles >> Testers (Add Testers)
Back in Customer Service Admin Center, navigate to Customer Support >> Channels >> Messaging Accounts (Manage)
Add a New Account
Click Next and provide the App ID and Application Secret
Add Facebook Page to the account
Provide the Page name, Page ID, and the Page access token.
With the page successfully added, click on Next
Copy the Callback URL and the Token.
Paste this information in the Messenger product added.
Click on Add Callback URL.
Click on Verify and save
This adds the Webhooks details, click on Add Subscriptions for the Page added.
Select messages
We can see the account added.
Open the record, and navigate to the Facebook Pages tab, there we can see the Provisioning state as Running.
Next, we will create a Channel for this Facebook Account.
Navigate to Customer Support >> Channels >> Messaging (Manage) >> Add Channel
Select Channel as Facebook.
Add an existing workstream or create a new workstream.
Next, select the Facebook Page configured in the previous steps.
Language as English.
We can specify custom automated messages and Post Conversation survey settings here.
Specify the File attachments setting and message tag.
Review and if required edit the details and finally click on Create channel to create the Facebook channel
Next open the workstream created, to specify routing rules, work distribution, bot, etc. to route the customers to the queues/agents.
Here we can create a Route to Queue ruleset to route the messages on the Facebook page to a specific Queue.
Create the ruleset record.
Next, Create a rule. We can define the conditions here (right now we are keeping it blank) and routing to the Default messaging Queue (we can create a specific queue and add only the required users).
Make sure you have added users to the Queue and assigned Omnichannel Agent security roles.
We can update the default Work distribution properties.
Now sending the message from the Facebook Messenger, will pop up the notification for the agent logged into Customer Service Workspace.
Accept the notification to start the conversation.
Refer to the below articles-
Hope it helps..
Recently while importing the solution in our UAT we got the below error –
It was showing the above entity relationships missing in the solution. We could not find them inside the Power Apps Maker Portal, to add them in the source solution.
Interestingly enough we were able to find them from the classic solution explorer.
Adding them to the source solution and trying the import fixed the issue for us.
Hope it helps..
Enhance Case Experience is currently available only for the Customer Service Workspace app which targets to increase the productivity of the agent.
To enable it, navigate to Customer Service Admin Center >> Customer Support >> Case Settings >> Enhanced case experience (Manage)
Enable the options – Here we have enabled the Full case form experience.
The new case form will show up while creating a new record from an existing case or the case grid.
Clicking on Configure opens the form in the Maker Portal.
The new Full Case form has the following new components added to it –
Grid Control – Case Associations (showing associated knowledge articles, similar cases, merged cases, and child cases)
More on Attachment control:https://nishantrana.me/2023/05/08/new-attachment-control-dynamics-365/
Due Activities Control – shows activities due today or overdue
More on Due Open Activities Control - https://nishantrana.me/2023/05/09/due-open-activities-control-dynamics-365/
It shows the activities overdue
More on Notes control - https://nishantrana.me/2023/05/10/notes-control-dynamics-365/
Get more details on Enhanced Case Form
Hope it helps..
Nishant Rana's Weblog 