Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Hi, I export data from the Dashboard but the some columns miss information (rows are enough). The file .pbix (Desktop version) and Dashboard that I upload on workspace are true, just the extracted excel file is lack of information. Can you please help me investigate and solve this problem? Many thanks!
Solved! Go to Solution.
Hi @Anonymous ,
Here are the limitations and considerations when exporting the data that was used to create a visualization. Please check if any one is the cause of the issue.
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:
- The column is defined as type "text" in the data model, and
- The first character of the text is one of the following: =, @, +, -
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.
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous ,
Here are the limitations and considerations when exporting the data that was used to create a visualization. Please check if any one is the cause of the issue.
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:
- The column is defined as type "text" in the data model, and
- The first character of the text is one of the following: =, @, +, -
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.
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Icey, thank you for your very detailed answer. I meet the problem you highlight. 2 tables I use "have many to many relation". Although the filter shows exactly the counting but the visualization misses some data. Just solve by move the columns from the second table to the end of the visualization.
@Anonymous
When you export data from a visual, you do not get the total columns and total rows, and, you will only get the data that is visible on the visual if the filters are applied.
Please explain further on the issue you are facing.
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
thank you for your answer. Yes, I find my visual lacks of data too although the filter shows exactly the number.
User | Count |
---|---|
94 | |
85 | |
78 | |
68 | |
63 |
User | Count |
---|---|
113 | |
99 | |
97 | |
64 | |
59 |