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

We will action “When an Http Request is received ” and follow below steps

1. Create Power automate Flow to receive HTTPS Request from Javascript and send Email
2. Register Javascript
3. Creating a Ribbon Button on Contact Entity and add javascript action to the button Command and pass PrimaryControl

As in our previous post we already mentions steps to register and use it in Javascript

Click Here : http://microsoftdynamics.in/2020/07/11/execute-microsoft-power-automate-from-ribbon-using-javascript-on-demand-power-automate-flow-using-javascript-in-uci-replace-ribbonaction-js/

Below code open request to execute power automate flow, Next step is to see how we can get Response message in JS

function readXML(executionContext) {   
var formContext = executionContext.getFormContext();
    var flowUrl = "Http Post URL";
    var input = JSON.stringify({
        "contactid": formContext .data.entity.getId().replace("{", "").replace("}", "")
    });
    var req = new XMLHttpRequest();
    req.open("POST", flowUrl, true);
    req.setRequestHeader('Content-Type', 'application/json');
    req.send(input);
}

In Step1, we had executed XMLHttpRequest and have not written code to get a response in JS, In this step we will add custom response message which we will get in Javascript .

1. Adding action “when a HTTP request is received”, setup payload
2. Adding Condition “1 = 1”
3. Adding Response action with Status = 200 and Body with Message “Yes Condition”

   

We have requested XMLHttpRequest to Execute Flow, Adding custom response msg in Power Automate,

Now we will use blow code to get response with status 200 in CRM

function readXML(executionContext) {   
var formContext = executionContext.getFormContext();
    var flowUrl = "Http Post URL";
    var input = JSON.stringify({
        "contactid": formContext .data.entity.getId().replace("{", "").replace("}", "")
    });
    var req = new XMLHttpRequest();
    req.open("POST", flowUrl, true);
    req.setRequestHeader('Content-Type', 'application/json');

////Response
req.onreadystatechange = function () {
        if (this.readyState === 4) { 
            req.onreadystatechange = null;
            if (this.status === 200) {
                var result = this.response; 
                alert("" + result); 
            }
            else if(this.status === 400){
                alert(this.statusText);
  var result = this.response; 
                alert("Error" + result);
            }
        }
    };  

////End
    req.send(input);
}

We can write the code to get request and get response Asynchronous or Synchronous Thanks

1. First approach is to use Upgrade examiner, please check out our last blog as below how to use Fast track and use upgrade examiner as a starter.

   

   Click Here: http://microsoftdynamics.in/2020/07/16/migration-from-legacy-webclient-to-uci-ask-for-fasttrack-and-upgrade-examiner-not-confident-on-transition-ask-microsoft/

2. Once you changed the latest client API’s there is a major change with Xrm.Page
   -> 1st enable checkbox ” Pass execution context as the first Parameter “-> ExecutionContext is Automatically passed as 1st parameter as below

   

Objective	Using Xrm.Page (Deprecated Client API)	Using formContext (Replacement Client API)
Simple JavaScript function	function demoFunction(){ }	function demoFunction(eContext){ //Get form context var formContext = eContext.getFormContext(); }
Disable/lock field, “addRegions”, for selection	Xrm.Page.getControl("addRegions"). setDisabled(true);	formContext.getControl("addRegions"). setDisabled(true);
Enable/unlock field, “addRegions”, for selection	Xrm.Page.getControl("addRegions"). setDisabled(false);	formContext.getControl("addRegions"). setDisabled(false);
Hide field, “addRegions”	Xrm.Page.getControl("addRegions"). setVisible(false);	formContext.getControl("addRegions"). setVisible(false);
Show field, “addRegions”	Xrm.Page.getControl("addRegions"). setVisible(true);	formContext.getControl("addRegions"). setVisible(true);
Get lookup field “region”, and its properties	var regionLookup = Xrm.Page. getAttribute("region").getValue(); if (regionLookup != null) { var name = regionLookup[0].name; var guid = regionLookup[0]. id.slice(1, -1); var entityType = regionLookup[0].entityType; }	var regionLookup = formContext. getAttribute("region").getValue(); if ( regionLookup != null) { var name = regionLookup[0].name; var guid = regionLookup[0]. id.slice(1, -1); var entityType = regionLookup[0].entityType; }
Remove option, 15220000, from ‘showRegions’ option set.	Xrm.Page.getControl("showRegions"). removeOption(15220000);	formContext.getControl("showRegions"). removeOption(15220000);
Add option, 15220001 (with text: ‘Africa’), to ‘showRegions’ option set.	Xrm.Page.getControl("showRegions"). addOption({ value:15220001, text:'Africa'});	formContext.getControl("showRegions"). addOption({ value:15220001, text:'Africa'});
Show tab, with logical name “regionsTab”	Xrm.Page.ui.tabs.get("regionsTab"). setVisible(true);	formContext.ui.tabs.get("regionsTab"). setVisible(true);
Hide tab, with logical name “regionsTab”	Xrm.Page.ui.tabs.get("regionsTab"). setVisible(false);	formContext.ui.tabs.get("regionsTab"). setVisible(false);
Show section “regionsTab_regSection”, located in tab “regionsTab”	Xrm.Page.ui.tabs.get("regionsTab"). sections.get("regionsTab_regSection"). setVisible(true);	formContext.ui.tabs.get("regionsTab"). sections.get("regionsTab_regSection"). setVisible(true);
Hide section “regionsTab_regSection”, located in tab “regionsTab”	Xrm.Page.ui.tabs. get("regionsTab").sections. get("regionsTab_regSection"). setVisible(false);	formContext.ui.tabs. get("regionsTab").sections. get("regionsTab_regSection"). setVisible(false);
Count number of records on sub-grid called “demo-grid”	var count = Xrm.Page. getControl("demo-grid").getGrid(). getTotalRecordCount();	var count = formContext. getControl("demo-grid").getGrid(). getTotalRecordCount();

Deprecated Client API	Replacement Client API	Comments
Xrm.Page	Forms: ExecutionContext.getFormContext Commands: Send it as the PrimaryControl parameter	Use of the Xrm.Page object as a static access to the primary form context is still supported to maintain backward compatibility with the existing scripts. Based on the feedback, we understand that the usage of Xrm.Page is high, and it won’t be removed as soon as some other client API methods listed in this section. We encourage you to use the new way of getting form content where possible. More information: Client API form context Although Xrm.Page is deprecated, parent.Xrm.Page will continue to work in case of HTML web resources embedded in forms as this is the only way to access the form context from the HTML web resource.
Xrm.Page.context	Xrm.Utility.getGlobalContext	Allows access to the global context without going through the form context.
Xrm.Page.context.getQueryStringParameters	formContext.data.attributes	The formContext.data.attributes API will make retrieval of non-entity bound data consistent across entity forms, metadata-driven dialogs, and task-based flows. The data will be a combination of custom values sent using the query string and what was specified in the parameters in the openForm method.
Xrm.Page.context.getTimeZoneOffsetMinutes	globalContext.userSettings.getTimeZoneOffsetMinutes	Moved to globalContext.userSettings
Xrm.Page.context.getUserId	globalContext.userSettings.userId	Moved to globalContext.userSettings
Xrm.Page.context.getUserLcid	globalContext.userSetings.languageId	Moved to globalContext.userSettings
Xrm.Page.context.getUserName	globalContext.userSettings.userName	Moved to globalContext.userSettings
Xrm.Page.context.getUserRoles	globalContext.userSettings.securityRoles	Moved to globalContext.userSettings
Xrm.Page.context.getIsAutoSaveEnabled	globalContext.organizationSettings.isAutoSaveEnabled	Moved to globalContext.organizationSettings
Xrm.Page.context.getOrgLcid	globalContext.organizationSettings.languageId	Moved to globalContext.organizationSettings
Xrm.Page.context.getOrgUniqueName	globalContext.organizationSettings.uniqueName	Moved to globalContext.organizationSettings
Xrm.Page.data.entity.getDataXml	No change in the method, but use “typename” instead of type for lookup attributes.
GridRow.getData	GridRow.data	GridRow is essentially a form context. This change unifies the interface of GridRow with formContext.
GridRowData.getEntity	GridRowData.entity	GridRowData is form data. This change unifies the interface of GridRowData with formContextData.
Xrm.Mobile.offline	Xrm.WebApi.offline	Moved the offline-related methods under Xrm.WebApi.offline
parent.Xrm	Use one of the following: a) Use a custom control created using Power Apps component framework instead of HTML web resources. b) On forms, use the getContentWindow method of the web resource control. c) If the getContentWindow method doesn’t work, you can use parent.Xrm to get to the Xrm object inside an HTML web resource. If the HTML web resource is opened in a new window then you should use opener.Xrm instead.	Earlier: An HTML web resource may interact with the Xrm.Page or Xrm.Utility objects within the form by using parent.Xrm.Page or parent.Xrm.Utility. Now: parent.Xrm.* will work if the HTML web resource is loaded in a form container. It won’t work for HTML web resources that are stand alone, or referenced from the site map or any other places. NOTE: parent.Xrm will be removed after the removal of the ClientGlobalContext.js.aspx page; dates yet to be announced.
addOnKeyPress	Use a custom control created using Power Apps component framework
fireOnKeyPress	Use a custom control created using Power Apps component framework
removeOnKeyPress	Use a custom control created using Power Apps component framework
showAutoComplete	Use a custom control created using Power Apps component framework
hideAutoComplete	Use a custom control created using Power Apps component framework
Xrm.Utility.alertDialog	Xrm.Navigation.openAlertDialog	The new signature is consistent with other APIs (openForm) and takes a new set of parameters for flexibility.
Xrm.Utility.confirmDialog	Xrm.Navigation.openConfirmDialog	The new signature is consistent with other APIs (openForm) and takes a new set of parameters for flexibility.
Xrm.Utility.getBarcodeValue	Xrm.Device.getBarcodeValue	Moving device-related actions to Xrm.Device
Xrm.Utility.getCurrentPosition	Xrm.Device.getCurrentPosition	Moving device-related actions to Xrm.Device
Xrm.Utility.isActivityType	Xrm.Utility.getEntityMetadata	The isActivityType method is synchronous so it was suitable for ribbon rules. However, the replacement method, getEntityMetadata, is asynchronous, and is not suitable for ribbon rules.
Xrm.Utility.openEntityForm	Xrm.Navigation.openForm	Moving navigation actions to Xrm.Navigation
Xrm.Utility.openQuickCreate	Xrm.Navigation.openForm	Moving navigation actions to Xrm.Navigation
Xrm.Utility.openWebResource	Xrm.Navigation.openWebResource	Moving navigation actions to Xrm.Navigation Note: This API returns VOID in Unified Interface.
globalContext.organizationSettings.baseCurrencyId	globalContext.organizationSettings.baseCurrency	The replacement method lets you access the display name along with the ID of transaction currency.
globalContext.userSettings.securityRoles	globalContext.userSettings.Roles	The replacement method lets you access the display name along with the ID of the security roles.
globalContext.userSettings.transactionCurrencyId	globalContext.userSettings.transactionCurrency	The replacement method lets you access the display name along with the ID of transaction currency.
getData and setData for Silverlight web resources	None	Silverlight is no longer supported. These methods won’t be available after October, 2020.
formContext.data.entity.save	formContext.data.save
ClientGlobalContext.js.aspx	None	The ClientGlobalContext.js.aspx page is built on the legacy web client infrastructure. As the legacy web client is deprecated and scheduled to be unavailable effective December 1, 2020, the ClientGlobalContext.js.aspx page will also be removed along with the legacy web client on December 1, 2020.
getObject	getContentWindow

Reference: https://docs.microsoft.com/en-us/power-platform/important-changes-coming#some-client-apis-are-deprecated

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 were preparing for the transition like doing validation of web resource forms etc but to be more confident we included Microsoft support and requested for Fast Track services.

What is Fast Track ?

FastTrack helps customers deploy Microsoft cloud solutions. Customers with eligible subscriptions to Microsoft 365, Azure, or Dynamics 365 can use FastTrack at no additional cost for the life of their subscription.

With Fast Track Service and Support, Microsoft Imported Upgrade Examiner , we will see the benefits of the same below

Although in our previous post we are doing Validation Entity wise considering all component to be tested, But this solution is also helpful

• It performs Validation on the list of component and provides suggestion and example what component needs attention

• If we Go through Entity Data and clicks Libraries, it gives us a list of Web resource with no of Remediation found

• and the coolest part is when we open any of the javascript it gives us the control to compare OLD CODE and NEW CODE (Suggested)

• In some cases, we can directly copy and past New code to the library but suggested to verify 1st.

SVG – Scalable Vector Graphics is most suitable for the Responsive page as it can be scaled high and keeping almost same Quality and that is the Reason these images suit the New UCI Responsive page. 

Below are some advantage for Using SVG

• SVG images can be created and edited with any text editor
• SVG images can be searched, indexed, scripted, and compressed
• SVG images are scalable
• SVG images can be printed with high quality at any resolution
• SVG images are zoomable
• SVG graphics do NOT lose any quality if they are zoomed or resized
• SVG is an open standard
• SVG files are pure XML

What are the changes we need to do

1. No change required for OOB system buttons when Transition happens it automatic updates
2. For Custom Button and Icon we need to Add SVG image in MorderImage Property from Ribbon workBench and we can keep Image 16 and image 32 if you want but it recommended we change them too.

So now we have 3 Properties control

1. Image 16 for 16*16 png or jpg image and used in classic Legacy WebClient
2. Image 32 for 32*32 png or jpg image and used in Classic Legacy WebClient
3. ModernImage SVG format independent of Resolution used in New UCI

Below are the steps to add SVG image in Modern Image

1. Create a New Web Resource with type as Vector Format (SVG) and Upload image

   

2. Now Open Ribbon WorkBench, If not installed install it from here
3. If button properties are disabled. right-click a select Customise button

   

4. Publish the Ribbon and we can now see the correct image in our Button at UCI.

• If your button not working most probably you are using RibbonAction or Ribbon Workflow , you might have used Ribbon Workbench to enable Command where using RibbonAction.js onto your ribbon button.

• so bad news is it has been Deprecated, below is the link from ribbon workbench Blog , you can go through it to remove it from Button

https://ribbonworkbench.uservoice.com/knowledgebase/articles/132235-create-a-workflow-short-cut-ribbon-button-no-code

• We can use JS to execute the Workflow or Action

• or I would recommend following this post:

• Execute Microsoft Power Automate from Ribbon using JavaScript – On-demand  Power automate flow using Javascript