Forum Discussion

naveenanda_vam's avatar
naveenanda_vam
Frequent Visitor
11 months ago
Solved

Exporting Power BI report using PBRS tool into .csv file , how to increase the row count

Hi, Good Day!!!   I am using one power bi report in service having 7 pages, every week on monday and first day of every month we are sending the extrcat in .csv file using PBRS tool to client . Bu...
  • tayloramy's avatar
    11 months ago

    Hi naveenanda_vam

     

    You’re running into a built-in export limit for standard Power BI report visuals. When tools (including PBRS) export data from visuals, the service enforces row caps - ~30,000 rows for CSV and ~150,000 for Excel - and PBRS can’t raise those limits because they come from Power BI itself. That’s why your job fails when one page returns more than the cap. See Microsoft’s “Export data from a visual” limits: Export data from a Power BI visualization. PBRS also documents that it inherits these limits from Power BI: PBRS export limitations.

    Quick solution

    • You can’t increase the CSV/visual export row limit. It’s by design. (Learn doc)
    • Use a Paginated Report (.rdl) for large flat exports and have PBRS (or Power BI) export that to CSV. Paginated exports don’t have a fixed row cap; they’re limited by capacity memory and timeouts. (Paginated report visual, and Microsoft confirmation that there’s no hard row cap: community post)
    • If you must stay with the current report pages, burst the export into multiple, filtered CSVs (e.g., by date or category) so each stays under the cap. PBRS supports filter/slicer-driven “bursting.” 
    1.  

    If this were my tenant, I’d move the “too-many-rows” page to a Paginated Report and have PBRS export that page to CSV on your Monday / month-start schedules. It’s the most reliable and cost-neutral way to deliver >150k rows.

     

    If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.