Forum Discussion
Incorrect DAX Query Generation for Export in Embedded Power BI Reports
Hi Anonymous,
Thank you for reaching out to Microsoft Fabric Community.
Currently power bi Embedded APIs do not expose visual level DAX queries, default slicer states or visible column state, this is a known limitation of Power BI Embedded.
If the requirement is to export exactly what the user sees, the only supported way is to use power bi’s built in export capabilities. Dynamically reconstructing visual queries using Embedded APIs will be partial and may not match the rendered output.
If this capability is critical, please consider submitting your detailed feedback and ideas through Microsoft's official feedback channels. Feedback submitted through these channels is frequently reviewed by the product teams and can contribute to meaningful improvements.
Fabric Ideas - Microsoft Fabric Community
Thanks and regards,
Anjan Kumar Chippa
Thanks Anjan Kumar. The default export functionality of Power BI is not good enough for our reports because many of the reports need to export more than 150K rows.
In our organization, Report Builder is not allowed.
Power Automate scripting will not work either: Due to the dynamic selection of the fields (using field parameters), users can select any set of fields. Writing a Power Automate script for such use case is becoming very complex.
so we are looking for the best recommended approach.
Is there any way to extract (not generate) the DAX query that the report uses?
Is there any way to extract (not generate) the DAX query that the report uses?Reports don't use DAX queries. Report visuals do use DAX queries. In a standard environment you can see the DAX query for each visual by using the "Export... Live connection" option and then examining the table query. But this may not be possible in an embedded scenario, and it is a manual process anyway.
