Test connection failed. Details: Error from token exchange: Runtime call was blocked because connection has error status: Enabled| Error, and microsoftforms is in the block list. Connection errors: [ParameterName: token, Error: Code: Unauthorized, Message: 'Failed to refresh access token for service: aadcertificate. Correlation Id=956F3FD8-14DB-48B2-8A59-B9E732BB4905, UTC TimeStamp=9/9/2020 2:12:54 PM, Error: Failed to acquire token from AAD: {"error":"invalid_grant","error_description":"AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '2020-05-21T13:20:41.4577451Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2020-08-24T18:29:02.0000000Z'. Trace ID: 93c8261e-a4e1-4d18-bac2-ce326c8a2d00 Correlation ID: e5643921-a39c-4216-b2ba-53fb5a80e988 Timestamp: 2020-09-09 14:12:54Z","error_codes":[50173],"timestamp":"2020-09-09 14:12:54Z","trace_id":"93c8261e-a4e1-4d18-bac2-ce326c8a2d00","correlation_id":"e5643921-a39c-4216-b2ba-53fb5a80e988","error_uri":"https://login.windows.net/error?code=50173"}']

We tried authenticating with the same user and it shows success but still getting above error, don’t know if this was some kind of bug but we tried several time and it was same.

Till the time we know, it was due to reset of password that happened last day. at the end we navigated to data -> connections. 

Which was asking to FIX CONNECTION for the user we were trying to authenticate. Click on FIX CONNECTION or Switch Account and it will fix it instantly

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

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
         }
    }
}

The scenario is When an Email is received to a ServiceSupport Queue System should automatically create a Case (or lead) then Send an Auto response email saying
“Dear Customer, We have created a case for this and our customer service agent will contact you in 24 hours, thanks”

So we have

• A ServiceSupport queue where we are receiving email.
• Then on that Queue itself or from service management, we will create  ” Automatic  Record  Creation and  Update  Rules “
• in “Automatic Record Creation and Update Rule”, we will “Specify Autoresponse  Settings” for auto-response email
• then we will “Specify Record Creation and Update Details” to add create action and conditions

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.