Export underlying data issue - even in import mode

[Anonymous]

Hi - I am getting export issue even in import mode while trying to export underlying data from visual.

Database: Azure SQL DB

Mode: Import

Visual has 3 measures.

Error:

[v-yuta-msft]

Hi cmaz,

Please check the limitation of export data below:

• The maximum number of rows that can be exported from Power BI Desktop and Power BI service to .csv is 30,000.

• The maximum number of rows that can be exported to .xlsx is 150,000.

• Export using Underlying data will not work if the data source is an Analysis Services live connection and the version is older than 2016 and the tables in the model do not have a unique key.

• Export using Underlying data will not work if the Show items with no data option is enabled for the visualization being exported.

• When using DirectQuery, the maximum amount of data that can be exported is 16 MB. This may result in exporting less than the maximum number of rows, especially if there are many columns, data that is difficult to compress, and other factors that increase file size and decrease number of rows exported.

• If the visual uses data from more than one data table, and no relationship exists for those tables in the data model, only data for the first table is exported.

• Custom visuals and R visuals, are not currently supported.

• Export data is not available for users outside of your organization who are using a dashboard that has been shared with them.

• In Power BI, a field (column) can be renamed by double-clicking the field and typing a new name. This new name is referred to as an alias. It is possible that a Power BI report can end up with duplicate field names but Excel does not allow duplicates. So when the data is exported to Excel, the field aliases revert to their original field (column) names.

• If there is unicode character in the .csv file, the text in Excel may not display properly. Although, opening it in Notepad will work fine. Examples of unicode characters are currency symbols and foreign words. The workaround for this is to import the csv into Excel, instead of opening the csv directly. To do this:

  1. Open Excel
  2. From the Data tab, select Get external data > From text.

• Power BI admins have the ability to disable the export of data.

Regards,

Jimmy Tao

[Anonymous · Accepted solution]

Hi Jimmy

Thanks for your reply. None of these limitations currently apply to the report in question.

I had a call with the Microsoft Power BI Pro support techie yesterday and showed him the issue on live meeting.

He asked me to send the file with dummy data to reproduce the issue in-house.

I am working on it.