Category: Power Platform#

Get your Power Automate Flow Metadata – Quick Review

Hi Folks,

Well this post talks about pretty basic but an important tip, it is the best way to get the flow Metadata.

Have you every got a requirement to get the Metadata about the flow you were running in…yes, then this post is for you.

Let’s say you were running a flow, you want to report out from when this flow has been running and Flow Guid etc…then Add the below action to get the details in a Compose step…

Run the flow to see the details retrieved…

If you carefully review the parameters returned..

{
"id": "/subscriptions/689ae050-9b02-4149-8b91-e748fd66aca1/resourceGroups/97AE7E352F87418B94326733950F3D5C-B3AADDB182B5EDD9A5AEBDFED80A2DD7-ENV/providers/Microsoft.Logic/workflows/f6dbb4bf-a18c-0908-d3a2-37e60692e32b",
"name": "f6dbb4bf-a18c-0908-d3a2-37e60692e32b",
"type": "Microsoft.Logic/workflows",
"location": "centralindia",
"tags": {
"flowDisplayName": "Child Flow ",
"capabilities": "Premium",
"environmentName": "b3aaddb1-82b5-edd9-a5ae-bdfed80a2dd7",
"logicAppName": "f6dbb4bf-a18c-0908-d3a2-37e60692e32b",
"environmentWorkflowId": "b3aaddb1:2D82b5:2Dedd9:2Da5ae:2Dbdfed80a2dd7-e0a7a57f:2D8c22:2Df011:2D998a:2D7ced8d27b0be",
"xrmWorkflowId": "e0a7a57f-8c22-f011-998a-7ced8d27b0be",
"environmentFlowSuspensionReason": "b3aaddb1:2D82b5:2Dedd9:2Da5ae:2Dbdfed80a2dd7-None",
"sharingType": "CommonDataService",
"state": "Enabled",
"createdTime": "4/26/2025 10:53:22 AM",
"lastModifiedTime": "4/27/2025 4:20:21 AM",
"createdBy": "31c73073-3c18-441d-a060-38b8a852f56e",
"triggerType": "Instant"
},
"run": {
"id": "/subscriptions/689ae050-9b02-4149-8b91-e748fd66aca1/resourceGroups/97AE7E352F87418B94326733950F3D5C-B3AADDB182B5EDD9A5AEBDFED80A2DD7-ENV/providers/Microsoft.Logic/workflows/f6dbb4bf-a18c-0908-d3a2-37e60692e32b/runs/08584558792611390446057643394CU13",
"name": "08584558792611390446057643394CU13",
"type": "Microsoft.Logic/workflows/runs"
}
}
view raw gistfile1.txt hosted with ❤ by GitHub

Inorder to read the JSON Object, let’s use Parse JSON..

Note that there were few important properties to take note..

  1. capabilities : It identifies whether Flow needs Premium Subscription
  2. environmentFlowSuspensionReason : It indicates if the exact reason when the flow had intermittenly terminated
  3. state:
  4. trigger type: It tells about the type of trigger which was used for the flow.

Hope this way, you can send email notification to support team to further investigate if there is any issue with the flow.

Cheers,

PMDY

Visualize this view – what this mean to developers and end users…?

Hi Folks,

Have you noticed Visualize this view button in in the app bar of any grid view of Dynamics 365?

Here is a dashboard built within couple of minutes. While this can greatly help end users visualize the data present in the system. So, in this post, let’s understand bit more details about this capability and what are the some of the features which are left behind.

Let’s understand the how’s this is generated along with its capabilities and disadvantages compared to traditional Power BI dashboard both from Developer and end user perspective, please note that this is my understanding..

For Developers:

a. Visualize this view uses a PCF Control which calls the Power BI REST API and then generates the embed token for the report embedding that into an Iframe.

b. Then uses Power BI JavaScript API to handle user interactions with the embedded report such as filtering or highlighting data points.

c. When Power BI first generates your report, it takes a look through your data to identify patterns and distributions and pick a couple of fields to use as starting points for creating the initial set of visuals when data is not preselected.

d. Any changes to the data fields calls the UpdateView of the PCF Control and there by passing the updated data fields to REST API and then displays the visuals.

e. Visuals will be created with both selected and non-selected fields which are the related to the selected fields in the data pane.

For End Users & Developers:

Advantages:

  1. Visuals are generated when no data is selected
  2. Cross Highlighting is possible
  3. Click on the Report to see Personalize this visual option
  4. People with Contributor, Member, or Admin role assigned can save the Report to workspace
  5. Users with no access to Power BI cant view this feature, they can request for free Power BI License
  6. Free License users can save the Report to thier personal workspace
  7. Users get build permission when any role above Contributor is assigned and reshare permission is given
  8. The report will be saved as direct query with SSO enabled and honours dataverse settings
  9. Show data table presents a list of tables if the model comprises of multiple tables.
  10. Able to specify the aggregation for each of the field in the model.

Disadvantages:

  1. Only able to export summarized data from Visuals, you will be able to export the data in table from data table.
  2. Only Visual Level, no page level or report level filters
  3. During these reports creation, the model is configured to use Direct Query with Single Sign On.
  4. Embed a report on a Dataverse form requires modifying the XML of the solution
  5. Report published into the workspace are available to download but downloaded reports will not be able to customize further in Power BI Desktop as it would be built using Native Queries.
  6. If the page is kept ideal for long time or the user navigates to other browser window, the session and report will be lost.

Considerations & Limitations:

  1. Power BI Pro license is required to create these reports
  2. While this is wonderful for end users to visualize the data but this is not an alteranative to building reports using Power BI Desktop.

Hope this helps.

Cheers,

PMDY