Managing and Exporting High-Volume Datasets (~1M Records) in Power BI

Hi Sidhant , Thank you for reaching out to the Microsoft Fabric Community Forum.

For the Paginated Report issue, the trick is to pass a single text parameter with all selected columns and then use that in the RDL column visibility expression. That prevents the all columns showing problem you mentioned.

On the Fabric + Power Automate side, Bad Request almost always points to the request body or authentication. I’d suggest testing the same call in Postman first, once it works there, copy the request into Power Automate. Pay special attention to the JSON structure and whether your service principal actually has contributor rights on the workspace.

For making exports user-friendly, instead of asking users to run external tools, you can give them a Power BI button linked to Power Automate. That button passes their selections into a Fabric pipeline or notebook, which generates the file in OneLake/Blob. The flow can then email them the file link or the file itself. That hides the complexity and keeps it to a couple of clicks for them.

Email subscriptions in Power BI don’t solve the row-limit issue, they’ll still be capped. But you can repurpose the idea by instead of subscriptions from the service, use your Power Automate flow to deliver exports on a schedule or on-demand, which gives the same experience without the limit.