Forum Discussion
Passing Dynamic Field Parameters from Power BI to Power Automate for Fabric Pipeline Execution
Hi Anonymous ,
In a recent project, I worked on integrating Power BI with Microsoft Fabric using Power Automate to trigger a pipeline based on dynamic field selections. The journey started with building a Lakehouse in Fabric using an Excel dataset. From there, I created a semantic model and connected it to Power BI for reporting.
To make the reports more interactive, I introduced field parameters in Power BI. These parameters allow users to dynamically select which fields they want to view or export. To capture these selections, I used a DAX expression that generates a comma-separated list of field names based on slicer input:
SelectedFieldsCSV =
VAR orders = VALUES('Selected Fields'[Selected Fields Order])
RETURN
CONCATENATEX(
FILTER('FieldParamText', 'FieldParamText'[Order] IN orders),
'FieldParamText'[RDLName],
","
)
This DAX measure returns the selected field names in the order defined by the slicer, which I then tried to pass into a Power Automate flow triggered from the Power BI report.
While the flow was successfully triggered, I ran into an issue: the SelectedFieldsCSV value was coming through as null. I attempted to access it using both a Compose action and an Initialize Variable step in Power Automate:
@{triggerOutputs()?['body/SelectedFieldsCSV']}
Unfortunately, both returned null. My goal was to use this value in an HTTP call to trigger a Fabric pipeline, but without the parameter, the call couldn’t be completed as intended.
Interestingly, when I used the same parameter in the Export to File for Paginated Reports action, it worked perfectly. That action uses built-in parameter mapping, and the value was accessible using:
"value": @{items('Apply_to_each')?['SelectedFieldsCSV']}
This suggests that the parameter is available within the rows → entity object, not directly at the root level of the trigger body.
So now I’m looking for guidance: how can I correctly extract SelectedFieldsCSV from the trigger payload and assign it to a variable or use it in an HTTP call? Has anyone successfully passed slicer-driven parameters from Power BI to Power Automate and used them in Fabric pipeline executions?
Any suggestions or examples would be greatly appreciated!
Hi Poojara_D12 ,
This end-to-end solution enables users to dynamically select fields in Power BI and export the filtered data to a well-formatted Excel file via Microsoft Fabric, with automation powered by Power Automate.
The flow begins with a Power BI report where users choose specific columns using slicers or parameters. A Power Automate flow—triggered via HTTP or a Power BI button—captures these selections, along with export metadata like user email, export ID, and record limits. The flow authenticates with Microsoft Fabric using an Azure App Registration and securely triggers a Fabric data pipeline.
Inside Fabric, the pipeline filters and exports the selected data to Excel, formats the output using a notebook (with headers styled, column widths adjusted, and summary metadata added), and stores it in a Lakehouse location. After processing, Power Automate fetches the file and emails it directly to the user, attaching the Excel file with all selected data.
This workflow is scalable, secure, and user-friendly—ideal for automated reporting, scheduled exports, or on-demand sharing. It eliminates manual data exports and delivers polished Excel reports with just one click from Power BI.
5 Replies
- Poojara_D12
Super User
Hi Anonymous
When you pass a DAX measure like SelectedFieldsCSV from Power BI into Power Automate using a button trigger, the value doesn’t sit at the root level of the trigger body but is instead nested inside the body/value array, which represents the rows returned by the dataset. That’s why trying to access it with triggerOutputs()?['body/SelectedFieldsCSV'] gives null, because Power Automate is looking in the wrong place. To correctly extract it, you need to reference either the first row of that array using @first(triggerOutputs()?['body/value'])?['SelectedFieldsCSV'] if you expect only one record, or use @items('Apply_to_each')?['SelectedFieldsCSV'] inside an iteration if multiple rows are possible. This matches what you observed in the paginated reports export, where Power BI automatically handled the row structure. Once you use the correct expression to target the nested field, the measure’s output will be available to assign to a variable or pass directly into your HTTP action for triggering the Fabric pipeline.
Hi Poojara_D12 ,
This end-to-end solution enables users to dynamically select fields in Power BI and export the filtered data to a well-formatted Excel file via Microsoft Fabric, with automation powered by Power Automate.
The flow begins with a Power BI report where users choose specific columns using slicers or parameters. A Power Automate flow—triggered via HTTP or a Power BI button—captures these selections, along with export metadata like user email, export ID, and record limits. The flow authenticates with Microsoft Fabric using an Azure App Registration and securely triggers a Fabric data pipeline.
Inside Fabric, the pipeline filters and exports the selected data to Excel, formats the output using a notebook (with headers styled, column widths adjusted, and summary metadata added), and stores it in a Lakehouse location. After processing, Power Automate fetches the file and emails it directly to the user, attaching the Excel file with all selected data.
This workflow is scalable, secure, and user-friendly—ideal for automated reporting, scheduled exports, or on-demand sharing. It eliminates manual data exports and delivers polished Excel reports with just one click from Power BI.
v-prasareCommunity Support
Hi Anonymous,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Poojara_D12, thanks for your prompt response
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support- v-prasare
Hi @ShubhaGampa11,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support - v-prasare
May I ask if you have resolved this issue? If so, Can you please share the resolution steps here. This will be helpful for other community members who have similar problems to solve it faster.
If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.
