PowerApps Portal – Perform CRUD Operation using Editable Subgrid

However, there are some limitations of Fetch XML:

• It can only run on Page Load.
• It cannot runs On-demand. Like on button click.
• Its sequence/order is always first on the page. Means, it always runs at the beginning of the page load. We cannot change it\’s running order. For Example: If I have to run the Fetch XML once my particular business logic is completed, then it is not possible.

Sometimes, we need to pass some information from Portal to CRM in order to perform some complex logic in Dynamics 365.
For Example- If I have a requirement to provide Approval functionality on the portal, where a specific set of users can approve the requests directly from the portal, And, in CRM we need to perform some complex business logic as soon as request status gets changed to Approved based on the user who Approved the request from Portal.
In this requirement, we could use the Entity List Workflow Action configuration, which lets you allow to run an on-demand workflow directly on Entity List\’s records. However, it doesn\’t provide any options to pass some information/parameters to the workflow. Like in our requirement, we need to pass the logged-in user id/name to know who approved the request.
Hence, we cannot implement such requirements directly from Portal and we end up writing either Plugin or Custom code to achieve this.

{% endfetchxml %}

In the highlighted JSON, All Bold texts are written after {{result. are the schema name of a CRM field. While the texts are written before the : (colon) are like variables, used to hold the field\’s value.

Step (h) Test the JSON

Open the Webpage (partial URL) in the browser, you should get the entity data in JSON format (as shown below:

Step 2 – Create a Power Automate to communicate between Portal and Dynamics 365

Step (a) Create a Power Automate (Instant – From blank).

Step (b) Provide Name of the Flow and Choose When an HTTP request is received as Trigger Point

Step (c) Click on Use sample payload to generate the schema. Paste your sample JSON and Click on Done. Make sure there is no white space or syntax mistake in your sample JSON

My Sample JSON:

{ \”lead\” : [{ \”Action\”:\”Create\”, \”RecordId\”:\”123123\”, \”Subject\”: \”powerappsportal\”, \”Firstname\”: \”Arpit\”, \”Lastname\”: \”Shrivastava\”, \”Email\”: \”arpit@gmail.com\”} ]}

In the above JSON, 

• lead –  is a kind of variable inside my JSON which holds the whole JSON string.
• Action – will hold the operation name like Create/Update/Delete, etc
• RecordId – will hold the guid of dynamics 365 records. We\’ll pass null value when we have to Create the record, while in case of Update and Delete, we need to pass the guid of the record
• Subject – hold subject of lead
• Firstname – hold first name of the lead
• Lastname – hold last name of the lead
• Email – hold email address of the lead

You just need to put some sample values (except the Bold ones) in the JSON when you paste it in the Sample JSON Payload screen (shown above). However, in your code (mentioned in Step 2), you need to pass the actual dynamic values in order to perform your business logic.

Step (d) Add Next Step and Select Initialize Variable (rename it as per your need). And provide values as shown below. To set the value:

• Click inside the Value input box, you\’ll see a small popup window next to it.
• Click on Expressions Tab inside the popup window.
• Paste –  triggerOutputs()[\’headers\’][\’origin\’] inside Expressions and Click OK

Open any Power Automate instance From Run History and You\’ll see the origin in HTTP Request Headers

• You will see the origin value set in your Value input box

Step (e) Add Next Step and Select Initialize Variable (rename it as per your need). Provide a Name and set it\’s Type to String (as shown below). Keep its value blank as of now. We\’ll set it\’s value later.

Step (f) Add Next Step and Select Apply to each

• Click inside the box Select an output from the previous step, you\’ll see the same popup window next to the input box.
• Choose the name of your JSON. In my example, the name of JSON is lead. (As shown below) Hence, it\’s showing a lead in the popup window

• We have to add the Conditions inside Apply to each as per the below diagram.

• So let\’s get started and Add first Condition Step inside Apply to each Step. And add the following 2 conditions to it.
• Action equal to \’Create\’ and
• Origin contains \’ or \’

• If Condition is True.
• Add Dynamics 365 Action and Choose to Create a record step

• Add one more step just below the Create a new record step and Choose Set Variable in order to set the variable (that we have initialized in Step (e)) value to Guid of the created record.

Open any Power Automate instance From Run History and You\’ll see the iteminternalid in Create a new record step

• If Condition is False
• Add one more Condition Step and again add following 2 conditions
• Action equal to \’Update\’
• Origin contains \’ or \’
• If Condition is True (Request is for Update and originated from Portal)
• Add Dynamics 365 Action and Choose to Update a record step

• If Condition is False
• Add one more Condition Step and again add following 2 conditions
• Action equal to \’Delete\’
• Origin contains \’ or \’
• If Condition is True (Request is for Delete and originated from Portal)
• Add Dynamics 365 Action and Choose to Delete a record step

• A complete view of all the Conditions inside Apply to each step:

Step (g) Add Next Step outside Apply to each and Choose Response Step to capture HTTP Request Request. We don\’t need to read the response in case of Update and Delete. However, in the case of Create we need to return the Guid of created record as a response. Hence, we are using this step to Create operation only.

Step (a) Create a new webpage as below

Step (b) Open the Localized Content record from the Webpage and Paste the code in Copy HTML Section (as shown below)

Download the complete code from GIT Hub

Code to call webpage (associated with web template) as WEB API to retrieve dynamics 365 data.

leadpage is the name of my webpage created in Step 1

I have used the following code on click of Refresh Icon, in order to refresh the table (if required) and get the updated data from Dynamics 365.

//Get the record Guid as a Response from Power Automate

Fill the form and Save the Information

The information has been Saved in Dynamics 365 and Showing in HTML Table

That\’s all folks.

Stay Tuned for next interesting Tip – PowerGuideTip10