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..
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 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..
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..
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..
We now have new Notes control for the Case table.
The new notes control allows us to associate/create note without the need to create the case record first.
Here we are adding the Notes control in our Case form.
Specify Pre Create Notes Id (Text) as Table Column for Bound Attribute.
Save and publish the changes.
On creating the record we can see notes added to the timelines.
Also, we can observe that the control now shows – “No Data Available”.
In the case of the Enhanced Case Form, we have a script that hides that section after creation.
Due Open Activities Control – https://nishantrana.me/2023/05/09/due-open-activities-control-dynamics-365/
Attachment Control – https://nishantrana.me/2023/05/08/new-attachment-control-dynamics-365/
Hope it helps..
Nishant Rana's Weblog 