We can see in the above image there is legacy data that is duplicate and was ignored and saved, but when Migrating to UCI the Entity list is having Editable control which does not allow to open record because of this duplicate rule but nor giving any exact error.

1. we can disable Editable gird control from the entity.

   

2.  We can do modification to duplicate rule as desired so we can avoid error in entity list

   

3. Or we can review Business Rule as well especially the one with Entity as the scope

   

Hoping this was helpful. thanks

As we can see in the above screenshot when we open an email from Sales Hub it doesn’t search for Queue record in TO or FROM fields and the same way if we open an email from Customer Service Hub it won’t search  Lead record.

As we know in Legacy Web client there was no setting available to include or exclude them except Javascript so it took us some time to accept there might be some configuration or setting we might be missing. and with some research, my college provided the information providing below community query and it was helpful. thanks to Clofly Mao

https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/361316/how-to-enable-the-email-from-field-to-include-queues-as-a-selection

So we can follow the below steps to add or remove entities from Model-Driven apps to show or hide them from Email entity but remember these are not only limited to Emails, if you remove any entity it will be removed from whole model-driven app.

1. Go to
   https://dvmske.crm8.dynamics.com/main.aspx?forceUCI=0&pagetype=apps
   and open app designer or best practice is to create a solution add your model-driven app to it and then edit the same.

   

2. Click on Entities which will open up a list of entities checked means added to the app

   

3.  Search for the entity missing

   

4. Check the entity and then scroll from Entity View to add forms or view to be available on the hub

   

5. Save and Publish

Same Way we can add lead fro the Customer Service hub and now Both entities will be visible in TO fields of the email.

As we know we can use WebHooks to creating external handlers for server events, like azure service bus  or any other web service.

in this post

1. we will create power automate with action as ” when an HTTP request is received”
2. Get HTTP Post URL, Will break the URL as URL and parameters
3. Register a webhook using the plugin registration tool
4. Register a step on the update of the account name.
5. Adding the “Response” action in power automate to see exception in CRM using webhook

1. Create Instant flow and select action “When a HTTP request is Received”  with Method as post and Payload generic

   

2. Once Saved we will get the URL , copy the URL and Break it down as below to specify HTTP query parameter in webhook.
   

   https://prod-25.centralindia.logic.azure.com:443/workflows/73a854555aaa5fad8f867ac168/triggers/manual/paths/invoke
   
   api-version=2016-06-01
   sp=/triggers/manual/run
   sv=1.0
   sig=Sxfp4x5V51JDEeSYuf4mvxTXlGR2xTxn3WeQiab00yY
   

1. Login to plugin Registration tool and register new WebHook with Below config and Http Post URL.

   

2. Now Register new Step on Update of Account entity, field = account name.

   

3. All Done, If we want to add some condition and throw an exception for any condition, we can do so by adding “response ” in  Power automate

   

It would be a kind of realtime exception even we know the flow is meant to be working in async.

• As per the Scenario, we added trigger as an update of the case with a filter as status should be equal to 5 (problem resolved)

  

• Now ideally we should get Environment URL in the Dynamic field OdataID as below but that will not come up when the trigger happens from CDS
• So we will use Action to Get Case using Trigger ID, We know its repeated step but this is needed to get Environment URL, and we can limit attribute retrieving. We are using Compose action to verify our output

  

• Here we get the full Odatat URL, not just the Environment URL, so we will be using an Expression uriHosts(outputs(‘URL’)
• Compose action: uriHosts(outputs(‘URL’) , Where outputs is output of compose and (‘url’) action name refer screenshot
• Other Action: uriHost(body(‘ActionName’)?[‘@odata.id’]) 

AppId can no be retrieved directly in Power automate.

1. we use a configuration ” organization config”  where we store multiple appid example sales hub , customer hub etc
2. We will use get record action to retrieve the required appid.

In Point 1 we got the environment url and from point 2 we know how to get AppId as well, but here we are not using appid and if we don’t use it that doesn’t it will automatically open it available app as per permission.

1. We created an Trigger as update of case
2. Using compose output and get record we got the Odata URL as well
3. Now we will initialize Variable just to get the final output of the dynamic record URL, we can do this directly in email as well.

   

4.  Now we will use Hyperlink or ancher html tag to use Record url in Email

   

In Output we can see our URL which can be with or withour CMDBAR and NAVBAR

1. Open Ribbon WorkBench
2. Select Solution contains entity and components
3. Add button, Add command
4. Now add Javascript Action and select Javascript and Function
5. Now Click on Add Parameter
6. Add CRM Parameter

   

7. and select Primary  Control

   

1 thing to remember, like for Form Button , always use PrimaryControl as Form Control

function readXML(executionContext) {   
 if (executionContext !== null) {

             formContext =  executionContext;  //PrimaryControl
   }
alert("executionContext  is null ");
}

We can create a new Queue if not already present

1. Navigate Setting -> Business Management -> Queues

   

2. Create a new Queue with email ID (remember we are not creating user as if support user is in created in the system it will have its own queue) also when queue is created it creates it mailbox

   

3. Once done Approve email then Test and Enable Mailbox

   

There are 2 ways to create “Record Creation and Update Rule”

1. Create a form Setting -> Service Management -> Select Automatic Record Creation and Update Rules
2. 2nd Way is to go to Quote and create ” Record Creation and Update Rule ” from subgrid

   

3. Fill in values as below

   

1. In Step three of ” New Record Creation and Update Rule” , There is a option to select Automatically reply to email = yes
2. Select an Email Template in lookup.
   Example: “Dear Customer, We have created a case for this and our customer service agent will contact you in 24 hours, thanks”

Once all Step above are saved, Go to Subgrid ” step two: Condition to Evaluate and Actions to take ” and for Legacy Web Client it will be “Specify Record Creation and Update Details”

1. Open ” RECORD CREATION AND UPDATE RULES”  once saved , click new from “SPECIFY RECORD CREATION AND UPDATE DETAILS”
   NOTE: Try doing this from the Legacy app as it might give error

   

2. Fill in details like Name and add conditions: Conditions are almost the  same as we add in Workflow or advance find query

   

3. Now we will add action, click Add Step, and select create a record. we will be presented with a list of entities , in our case, we will select case,

   

4. Once Done Save and Close the record.

Last Step is to Activate the Automatic Record Creation and Update Rule

There are 2 Option

1. Remove Category Tracked to Dynamics 365 using setting from OrgDBOrgSetting/Releases and same can be used to Enable setting
   https://github.com/seanmcne/OrgDbOrgSettings/releases/

   

2. From admin.powerplateform.microsoft.com disable setting-> Access https://admin.powerplatform.microsoft.com as an administrator
   -> On the Environments tab, click … next to the name of the environment and then click Settings.
   -> Click Email Tracking.
   

   

   -> Locate the option People can use categories to track emails and appointments and switch the option to Off.

->Disabling this setting will remove the category Tracked to Dynamics 365 on all Exchange mailboxes of the Dynamics 365 for Customer Engagement organization which have server-side synchronization enabled in about 15 minutes.