Forum Discussion
Export Data - Data Exceeds the Limit
Hi,
I suspect this comes with the November update. When I try to do an Export Data from a Matrix or Table I am now getting a Data Exceeds the Limit error, I used to be able to Export data with a wide date range but after the update it's now giving me that even if I select a single date to export.
What's going on?
Hey,
the documentation states that there is a limit of rows that can be exportet to csv, this limit is 30000 rows.
Using the target format xlsx this limit is 150k rows, the export to xlsx option is available in Power BI Service.
These limits are described here:
https://docs.microsoft.com/en-us/power-bi/power-bi-visualization-export-data
Please don't ask me why such a limit exists :-) I'm just the messenger
Regards
Tom
35 Replies
ovetteabejuela,
I can reproduce your issue in November update. Based on my test, the message will throw when you export >=500 rows data. When your visual contains >=500 rows data, as long as you click "Continue" button, the data will be exported in CSV properly.
Besides, I will report this issue internally and post back once I get any updates.
Regards,
LydiaThank you for looking and kindly post back. Okay so the "Continue" option will not truncate anything?
As of now I recreated everything in Excel PowerQuery just for that portion where we need the data exported in CSV.
ovetteabejuela，
When I test with 10000 rows and use Export data option, the data are not truncated, but for the specific limit, we still wait for PG's response.
Regards,
Lydia
ovetteabejuela,
The fix of this issue will be released on January.
Regards,
LydiaAnonymous,
Looking forward for the fix, thank you.
I too have this issue - and running on the Jan '18 update.
What is the status on this issue??
I'm running the Version: 2.56.5023.942 (March) and still have the same issue. Also, it seems a maximal number of rows which can be exported is 30000!
I am having this same issue. It sounds like you've confirmed it will not truncate the data at least up to 10,000 records, but how do we know for sure when receiving the error. We're supposed to be able to download 150,000 records. I am unsure as to whether or not I have a complete data set when using this feature.
Every release of Power BI seems to result in more bugs. These new bugs every month waste so much time. It's really frustrating.
I'm facing the same issu with the Version: 2.56.5023.942 (March) . It seems a maximal number of rows which can be exported is 30000!
Yes, apparently. Also it's still is doing that thing where it removes duplicate columns, well different headers but the same content - not a good design but yes I really intended to put a duplicate column. PowerBI removes the twin column and leaves only one.
You can't, unless you count the rows in your visual. As a workaround, I suggest using the October version until this gets fixed permanently,
As a temporary workaround, you can try reverting to the October version or you can ignore the warning for datasets smaller than 30k rows.
What more I have observed is that if it reaches a certain number of rows, it removes duplicate columns which I intentionally placed but if it's less rows it just leaves duplicate columns alone.
So probably I could say it does not truncate by rows(to a certain number maybe 30K or 100K) but it certainly does remove duplicate columns.
I will test this tomorrow morning. If you have any datasets you have used in your tests please share. Thank you.
I'm running the Version: 2.56.5023.942 (March) and still have the same issue. Also, it seems a maximal number of rows which can be exported is 30000!
Looks like, as a workaround here - I was able to make an RDL that utilizes the Power BI report in question (mine had 85,000+ rows). The RDL was just a simple table replicating the entire dataset (all columns). The Export of the RDL to Excel within Power BI Premium worked fine. I then embedded the RDL inside the Power BI Report for ease-of-interface for the users.
