Explaining Unified client interface URL Parameter and how it dynamically change the value while navigating to different pages

Table of Contents:

00:00 – Introduction
00:29 – UCI Dynamics URL parameters
01:32 – Unified client Interface URL Explained
03:16 – Cmdbr or command bar
03:54 – NavBar or Navigation Bar
04:23 – Create a power automate the flow
06:39 – Get Environment URL in Power automate
08:19 – Create Dynamics Record URL in ms Flow
10:31 – Add dynamics URL in Email

As per the above image, the URL contains 3 parts

1. URL of Environment: when we talk about the dynamic Record URL it should also consider when we move from UATto production we should not change it in the Production manual it should automatically take the URL of Environment.DVMSKEUAT.CRM.Dynamics.com to DVMSKEPROD.CRM.Dynamics.com
2. App ID: Each App has it unique Id if you want that Entity to open in a specific App we need to Define it in the URLappid = GUID
3. CMD Bar: CRM Bar is the bar where we navigate throw cmd buttons. We can remove/add-in from window by putting cmdbar= false/true

   

4. NavBar: This is the Blue bar of CRM where we navigate app and entity history, We can Remove/add in form window by setting navbar=on/off
   

• PageType: it is used to define type of page , Example pagetype=dashboard , pagetype=entitylist , pagetype=entity  E.T.C

  

• ENT: ent stands for Entity where we define the name of entity example account, contact, incident in our case
• ID: this defines GUID unique id of the page type or entity we want to retrieve data for example if we  using pagetype= Dashboard it will need GUID of Dashboard

Thank you.

There is a new command available in UCI to help us troubleshoot the ribbon, It will show Button Properties, Command Properties like Action, Enable Rule, Display rule, and the best part is we don’t have to install any tool or enable anything.

We just need to add these parameters in the entity “&flags=FCB.CommandChecker=true&ribbondebug=true”

• It can be an entity
  

  https://dvmske.crm8.dynamics.com/main.aspx?appid=68968382-8ff4-ea11-a815-000d3a3dfcae&forceUCI=1&pagetype=entitylist&etn=account&viewid=00000000-0000-0000-00aa-000010001001&viewType=1039&flags=FCB.CommandChecker=true&ribbondebug=true
  
  

• It can be a form
  

  https://yourOrg.crm8.dynamics.com/main.aspx?appid=68968382-8ff4-ea11-a815-000d3a3dfcae&forceUCI=1&pagetype=entityrecord&etn=account&id=aaa19cdd-88df-e311-b8e5-6c3be5a8b200&flags=FCB.CommandChecker=true&ribbondebug=true
  
  

• It can be Sub Grid

 

When we click on Command Checker

• It Gives us all Buttons available in Command Bar with property Hidden with name

• Clicking on Button, it will elaborate more on Button Property and  Command Property, Example in below we are checking why Activate button is hidden, and in Command Properties, we can see display rule resulted in false and we can check which condition failed

This is much helpful in this time where most of us are transitioning from legacy to UCI and get many buttons which are hard to identify why they are not visible in UCI but same in visible in legacy WebClient. Thanks

In Our last post we dynamically created Record URL in power automate but skipped Appid part ,

Click here for: http://microsoftdynamics.in/2020/09/12/uci-get-entity-record-url-or-generate-dynamic-record-url-of-a-record-in-power-automate-using-cds-connector-and-variable/

Below are the steps

• Create an entity “Organization Config” and create 2 fields,
  Sales hub App ID and Service Hub App ID

• Add Entity in Model-Driven App and side map where ever we want to keep it

• Now We will open our Power automate flow we created in the last post, Add an action “List Records”

• As we are using List Records which will give multiple results, we can use Odata filter or Fetch XMl to fetch the records

  

• This action gives Collection as output, we will use the below expression to get value from 1st record.
  

  body('get_org_config_list')?['value']?[0]?.dvm_salesappid

  

• Now we will use compose action output in our variable

  

The Scenario we had is when a case is resolved, send an email to the manager of the record that the Case is resolved including Record URL.

As per the above image, the URL contains 3 parts

1. URL of Environment: when we talk about the dynamic Record URL it should also consider when we move from UATto production we should not change it in the Production manual it should automatically take the URL of Environment.DVMSKEUAT.CRM.Dynamics.com to DVMSKEPROD.CRM.Dynamics.com
2. App ID: Each App has it unique Id if you want that Entity to open in a specific App we need to Define it in the URLappid = GUID 
3. CMD Bar: CRM Bar is the bar where we navigate throw cmd buttons. We can remove/add-in from window by putting cmdbar= false/true

   

4. NavBar: This is the Blue bar of CRM where we navigate app and entity history, We can Remove/add in form window by setting navbar=on/off
   

   

5. PageType: it is used to define type of page , Example pagetype=dashboard , pagetype=entitylist , pagetype=entity  E.T.C

   

6. ENT: ent stands for Entity where we define the name of entity example account, contact, incident in our case
7. ID: this defines GUID unique id of the page type or entity we want to retrieve data for example if we  using pagetype= Dashboard it will need GUID of Dahsboard

The post is Divided into 2 Parts

1. Executing PowerAutomate Flow from Button using javascript
2. Configuring response action in Power automate and Capturing response message in CRM using javascript

We got this error in UCI and not in Legacy WebClient,

1. We were Passing CRM Parameter PrimaryControl to Button in Ribbon workbench

   

2. In JS we were getting FormContext from primaryControl(Executioncontext) which was working fine in the Legacy app
   

   function readXML(primaryControl) {   
   var formContext  = null;
    if (primaryControl!== null) { 
               formContext = primaryControl.getFormContext(); 
            }
       }
   }

3. But when same is called in UCI we get ” ” Script Error, Because here we need to treat primary control as formContext

   

So final change needed in Code is as below

function readXML(primaryControl) {   
var formContext  = null;
 if (primaryControl!== null) {
         if (typeof primaryControl.getAttribute === 'function') {
             formContext = primaryControl; //called from the ribbon.
         } else if (typeof primaryControl.getFormContext === 'function' 
                 && typeof(primaryControl.getFormContext()).getAttribute === 'function') {
            formContext = primaryControl.getFormContext(); // most likely called from the form via a handler
         }
    }
}

There are some big changes in Client API and most of them are as below

• Execution Context: Context of any item on the form (Xrm.Page)
• Global Context: utility to retrieve org Information example, userID e.t.c  (Xrm.utility)
• Deprecated Client Apis and Intrrotucing some new

We will Divide the post in 2 parts

1. Replace Deprecated Client API To New and latest Client Api’s
2. Full Deprecated Client API vs new and Latest Client API’S Table

From Event Handler Property we can simply enable checkbox  “Pass execution context as first parameter ” and use that for Form Context as Below

And we can get FormContext from 1st parameter Execution Parameter.

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

             formContext =  executionContext.getFormContext();
   }
alert("executionContext  is null ");
}