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

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 ");
}

As in out last post, we added an HTML and js Web resource to enable Rich text editor control to a field without importing any 3rd party Solution, please refer the link below if still wants it in the legacy app.

Click Here: http://microsoftdynamics.in/2020/07/16/rich-text-editor-html-designer-for-microsoft-dynamics-365-crm-using-javascript-no-pcf/

Now the good news is we don’t have to write or use 3rd party PCF control or solution to enable Rich-text HTML editor Control, this is enabled when enabling Early access to 2020 release wave 2. and there are many other post can be checked from Nishant’s sir post where he explained

1. How to enable early access to 2020 release Wave 2: Click Here
2. Check other Posts on release 2020 wave 2: Click Here

1. Select the multiple-line text field, below we selected description field of Knowledge article
2. Go to Controls and click add control, Select Rich Text editor control and ADD

   

3. Select where to enable here you can see all devices are compatible and that’s due to the responsiveness of UI

   

4.  Save and publish and field will be enabled with Rich-text HTML control.
   Note: only for UCI forms

   

References :

Posts on 2020 Release wave 2 – Dynamics 365

https://docs.microsoft.com/en-us/dynamics365-release-plan/2020wave2/

We would be using Contact and campaign N:N Custom Relationship when Contact is created get source campaign from lead and map with contact.

1. Create new Automated Flow

   

2. Name the Flow and Choose Trigger, in our case its creation of record contact

   

3. Get Lead Record Item Unique id as Lead Source, To get source Campaign ID

   

4. Now We have Source Campaign ID from Lead and Contact Id, But to use relate Action we need OData URL for a related entity that is Campaign
   https://organizationName.crm8.dynamics.com/api/data/v9.0/campaigns(0d8dda4c-126e-e911-a980-000d3ae4c063)
   Where GUID will be mapped with Dynamics field value campaign ID

   

5. Selecting Action Relate record this action, Select Primary Entity i.e contact, Map Contact unique id, Relationship Name, URL

   

Save and Turn On the flow. Now each time contact is created and source lead contains campaign both will be associated using relate action.

Unrelate Action can be used to Disassociate the record same way.