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 . But recent days export failing due to more row count ( more than 150000 which is limit) i have cross verified individual sheet wise, so i found one of the sheet having issue which is extracting more than limit of row count which is power bi providing.  We are using PPU licenec. Kindly suggest me how can i increase the row count of CSV file so i can extract the data helping of PBRS tool.  Still if any other sources can extract which is not impacting of price

Need Help
  • tayloramy's avatar
    tayloramy
    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.

5 Replies

  • tayloramy's avatar
    tayloramy
    Icon for Super User rankSuper User
    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.

    • naveenanda_vam's avatar
      naveenanda_vam
      Frequent Visitor
      11 months ago

      i have seen one solution as mentioned below, is this can work to increase the rows which we can export from power bi into CSV file. i am using PPU licence 

       

      To increase the "Max Result Row Count" in Power BI Premium capacity, follow these steps:

      Steps to Increase Max Result Row Count

      1. Sign in to Power BI Admin Portal
        You need to be a Power BI admin or capacity admin to access these settings. Go to https://app.powerbi.com and sign in with your admin account.
      2. Go to Capacity Settings
        • In the left navigation pane, click on Admin portal.
        • Under Capacity settings, select the Premium capacity where your workspace/report is hosted.
      3. Adjust Max Result Row Count
        • In the capacity settings page, find the setting called Dataset settings or similar, and look for Maximum result rows returned by direct query/export operations or Max Result Row Count.
        • The default is often set to 150,000 rows limit. Increase this number according to your requirement and available capacity resources.
      4. Save Changes
        After adjusting the value, save or apply the changes.
      5. Restart or Refresh Capacity (optional but recommended)
        Some capacity settings require a restart or some time to take effect. You can restart the capacity or wait for the propagation.
      6. Test the Export
        After increasing the limit, test exporting the report or dataset again via PBRS to ensure that the larger row export works now.
      • tayloramy's avatar
        tayloramy
        Icon for Super User rankSuper User
        11 months ago

        Hi, 

        I'm not sure where these instructions came from, but when I look at my capacities (both P sku and F sku) I do not see any option like this. 
        There is also no way to "restart" the capacity. 

         

        All official documentation state that this 150k row limit is fixed. 

         

        One workaround you can do is export the 150k rows to excel, and then in excel edit the PQ query to change the max rows returned - though I warn you this could impact your capacity usage greatly if set too high. I have been able to successfully export 1 million rows like this, however at that point the excel file becomes very hard to work with, which is why thje default is 150k. 

         

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

  • v-prasare's avatar
    v-prasare
    Icon for Community Support rankCommunity Support
    11 months ago

    Hi naveenanda_vam,

    We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.


    tayloramy ,Thanks for your prompt response

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support

  • v-prasare's avatar
    v-prasare
    Icon for Community Support rankCommunity Support
    11 months ago

    We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

     

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support