Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hello,
I have a client, in which he is unable to export the data to excel from a table in PowerBI Web. This export worked until adding two more fields in this matrix.
If I remove these two fields and export, it works. However, I tested the export only with these two fields and the metrics in the table and it worked too.
There is some limit in terms of the number of levels in an export matrix?
Thank you.
José
Solved! Go to Solution.
Hi @JosePer ,
You can test if you can export data by reducing the number of rows and keeping the number of columns the same.
The following is Limitations about export data.
These limitations and considerations apply to Power BI Desktop and the Power BI service, including Power BI Pro and Premium.
To export the data from a visual, you need to have Build permission for the underlying dataset.
The maximum number of rows that Power BI Desktop and Power BI service can export from an import mode report to a .csv file is 30,000.
The maximum number of rows that the applications can export from an import mode report to an .xlsx file is 150,000.
Export using Underlying data won't work if:
the version is older than 2016.
the tables in the model don't have a unique key.
an administrator or report designer has disabled this feature.
Export using Underlying data won't work if you enable the Show items with no data option for the visualization Power BI is exporting.
When using DirectQuery, the maximum amount of data that Power BI can export is 16-MB uncompressed data. An unintended result may be that you export less than the maximum number of rows of 150,000. This is likely if:
There are too many columns. Try reducing the number of columns and exporting again.
There's data that is difficult to compress.
Other factors are at play that increase file size and decrease the number of rows Power BI can export.
If the visualization uses data from more than one data table, and no active relationship exists for those tables in the data model, Power BI only exports data for the first table.
Power BI custom visuals and R visuals aren't currently supported.
In Power BI, you can rename a field (column) by double-clicking the field and typing a new name. Power BI refers to the new name as an alias. It's possible that a Power BI report can end up with duplicate field names, but Excel doesn't allow duplicates. So when Power BI exports the data to Excel, the field aliases revert to their original field (column) names.
If there are Unicode characters in the .csv file, the text in Excel may not display properly. Examples of Unicode characters are currency symbols and foreign words. You can open the file in Notepad and the Unicode will display correctly. If you want to open the file in Excel, the workaround is to import the .csv. To import the file into Excel:
Open Excel.
Go to the Data tab.
Select Get external data > From text.
Go to the local folder where the file is stored and select the .csv.
When exporting to .csv, certain characters will be escaped with a leading ' to prevent script execution when opened in Excel. This happens when:
Power BI admins can disable the export of data.
If a dynamic format string is applied to a measure, the exported data would not preserve this formatting in Excel.
Wish it ish helpful for you!
Best Regards
Lucien
Hi @JosePer ,
Hi @JosePer ,
You can test if you can export data by reducing the number of rows and keeping the number of columns the same.
The following is Limitations about export data.
These limitations and considerations apply to Power BI Desktop and the Power BI service, including Power BI Pro and Premium.
To export the data from a visual, you need to have Build permission for the underlying dataset.
The maximum number of rows that Power BI Desktop and Power BI service can export from an import mode report to a .csv file is 30,000.
The maximum number of rows that the applications can export from an import mode report to an .xlsx file is 150,000.
Export using Underlying data won't work if:
the version is older than 2016.
the tables in the model don't have a unique key.
an administrator or report designer has disabled this feature.
Export using Underlying data won't work if you enable the Show items with no data option for the visualization Power BI is exporting.
When using DirectQuery, the maximum amount of data that Power BI can export is 16-MB uncompressed data. An unintended result may be that you export less than the maximum number of rows of 150,000. This is likely if:
There are too many columns. Try reducing the number of columns and exporting again.
There's data that is difficult to compress.
Other factors are at play that increase file size and decrease the number of rows Power BI can export.
If the visualization uses data from more than one data table, and no active relationship exists for those tables in the data model, Power BI only exports data for the first table.
Power BI custom visuals and R visuals aren't currently supported.
In Power BI, you can rename a field (column) by double-clicking the field and typing a new name. Power BI refers to the new name as an alias. It's possible that a Power BI report can end up with duplicate field names, but Excel doesn't allow duplicates. So when Power BI exports the data to Excel, the field aliases revert to their original field (column) names.
If there are Unicode characters in the .csv file, the text in Excel may not display properly. Examples of Unicode characters are currency symbols and foreign words. You can open the file in Notepad and the Unicode will display correctly. If you want to open the file in Excel, the workaround is to import the .csv. To import the file into Excel:
Open Excel.
Go to the Data tab.
Select Get external data > From text.
Go to the local folder where the file is stored and select the .csv.
When exporting to .csv, certain characters will be escaped with a leading ' to prevent script execution when opened in Excel. This happens when:
Power BI admins can disable the export of data.
If a dynamic format string is applied to a measure, the exported data would not preserve this formatting in Excel.
Wish it ish helpful for you!
Best Regards
Lucien
Hi. This is odd. Are you connecting with direct query? That's the only way to be limitated in columns. It's not actually a column limitation but a size of matrix. Direct Query will only handle 16mb to export. You can read more about this limitations here:
I hope that helps,
Happy to help!
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.