Forum Discussion
Passing Dynamic Field Parameters from Power BI to Power Automate for Fabric Pipeline Execution
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.
Super UserHi 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.