The idea is for MS to fix the export to excel option from a visual.
Currently this is limited to 150000 rows export, but that's an underlying data processing limitation, not strictly the number of rows in the visual.
This is incredibly confusing to my user base, and has lead to multiple support incidents where data is missing without warning and the full set of data cannot be exported correctly for analysis/reconciliation
Why is there even a limit here? It really isn't resource intensive to stream out a dataset to a file.
Even the csv export from powerbi desktop is limited to 30000 rows, which strikes me as ridiculous: there's no server capacity used at all while streaming a query to a csv file that would need limiting, it seems completely arbitrary.
Please consider removing these limits.
on:
Dataverse tables not showing up in Power BI
on:
Fix export to excel from visual.
v-xiaoyan-msft
on:
Multiple updates are triggered by a single schedul...
Hi @andyclap ,
Thanks for your feedback! If you would like to suggest feature improvements, you may vote the idea and comment here to improve this feature. It is the right place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.
Best Regards,
Community Support Team _ Caitlyn