Power Platform Community Forum Thread Details

Help with recurring Power Automate use case

Our various reporting processes generate a number of edit lists that we'd like to push to users for issue resolution. So, a report generates the list of issues, and then I'd like to use a flow to process those results into output that's sent to the user.

Example: I'm running a DAX query against a published semantic model (output sample below). The query returns a list of issues with -- among others -- columns for PrimarySolicitor and PrimarySolicitorEmail. At the end of the flow, I'd like to have a single table (HTML table, e.g.) sent once via email to each PrimarySolicitor with all rows from the report output that contain that PrimarySolicitor's email.

Parse JSON has been a serious pain so far, so I'm wondering about using a Select action to get straight into First table rows from my DAX query output to start to format my end product. I'm eager to see what a best practice looks like for this use case.

Thank you!

{
    "statusCode": 200,
    "headers": {
        "Cache-Control": "no-store, must-revalidate, no-cache",
        "Pragma": "no-cache",
        "Transfer-Encoding": "chunked",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
        "X-Frame-Options": "deny",
        "X-Content-Type-Options": "nosniff",
        "RequestId": "REDACTED",
        "Access-Control-Expose-Headers": "RequestId",
        "x-ms-client-region": "unitedstates",
        "x-ms-flavor": "Production",
        "X-Ms-Workflow-Resourcegroup-Name": "selfhostingresourcegroup",
        "x-ms-workflow-subscription-id": "REDACTED",
        "x-ms-environment-id": "REDACTED",
        "x-ms-tenant-id": "REDACTED",
        "x-ms-subscription-id": "REDACTED",
        "x-ms-dlp-re": "-|-",
        "x-ms-dlp-gu": "-|-",
        "x-ms-dlp-ef": "-|-/-|-|-",
        "x-ms-mip-sl": "-|-|-|-",
        "x-ms-au-creator-id": "REDACTED",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "false",
        "x-ms-apihub-obo": "false",
        "Date": "Mon, 24 Nov 2025 23:05:28 GMT",
        "Content-Type": "application/json",
        "Content-Length": "543574"
    },
    "body": {
        "results": [
            {
                "tables": [
                    {
                        "rows": [
                            {
                                "All Proposals Table[ProposalId]": "VALUE",
                                "All Proposals Table[ProposalURL]": "VALUE",
                                "All Proposals Table[ProposalAmount]": VALUE,
                                "All Proposals Table[ProposalStage]": "VALUE",
                                "All Proposals Table[PrimarySolicitorUserId]": "VALUE",
                                "All Proposals Table[PrimarySolicitor]": "VALUE",
                                "All Proposals Table[PrimarySolicitorEmail]": "VALUE",
                                "All Proposals Table[ProposalName]": "VALUE",
                                "All Proposals Table[ProposalConstituentName]": "VALUE",
                                "[ProposalDesignationSum]": VALUE
                            },
                            {
                                "All Proposals Table[ProposalId]": "VALUE",
                                "All Proposals Table[ProposalURL]": "VALUE",
                                "All Proposals Table[ProposalAmount]": VALUE,
                                "All Proposals Table[ProposalStage]": "VALUE",
                                "All Proposals Table[PrimarySolicitorUserId]": "VALUE",
                                "All Proposals Table[PrimarySolicitor]": "VALUE",
                                "All Proposals Table[PrimarySolicitorEmail]": "VALUE",
                                "All Proposals Table[ProposalName]": "VALUE",
                                "All Proposals Table[ProposalConstituentName]": "VALUE",
                                "[ProposalDesignationSum]": VALUE
                            },

Categories:

Business Process Flows

Here’s a clean pattern that avoids Parse JSON and gets you to “1 email per Primary Solicitor with their rows:

1. Get the rows array from the DAX output (no Parse JSON)
After your “Run DAX query” action, add a Compose – Rows:
inputs:
first(body('Run_DAX_query')?['results'])?['tables'][0]?['rows']

2. Get a distinct list of PrimarySolicitorEmail values

Select – Emails
- From: outputs('Compose_-_Rows')
- Map:
  - Email →
  - item()?['All Proposals Table[PrimarySolicitorEmail]']
Compose – DistinctEmails
- Inputs:
- union(body('Select_-_Emails'), body('Select_-_Emails'))

3. Loop per email, build HTML table, and send once
Apply to each – DistinctEmails

Filter array – RowsForThisEmail
- From: outputs('Compose_-_Rows')
- Condition:
- item()?['All Proposals Table[PrimarySolicitorEmail]']
- is equal to
- items('Apply_to_each_-_DistinctEmails')?['Email']
Create HTML table – SolicitorTable
- From: body('Filter_array_-_RowsForThisEmail')
- (Optionally set custom columns)
Send an email (V2)
- To: items('Apply_to_each_-_DistinctEmails')?['Email']
- Body: outputs('Create_HTML_table_-_SolicitorTable')

🚀 Automate. Optimize. Innovate. 🚀

Helping businesses streamline workflows and maximize efficiency with Microsoft Power Platform. Let’s transform your processes and unlock new possibilities!

Explore BabyBots.ai

Quick Links