PBI Desktop unable to Export table data - Data exceeds limit

[TimHilverts]

Since the update of the following version; 2.121.644.0 (64 bits) we are facing issues while trying to export data from the visual. 

The dataset below contains 1000 rows, which would be not even close to the limit of 30,000 rows according to the documentation found here:

https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-export-data?tabs=powerbi-d...

Please fix this issue ASAP, many thanks!

[v-shex-msft · Accepted solution]

Hi @TimHilverts,

In fact, this is a known export issue(it not same as the export 300 rows issue). Power bi team are working on it , and I will update here if any ETA.

Update: 

This issue has been fixed by power bi team and will be apply to the new verison(v. 2.121.903.0) release soon.

Regards,

Xiaoxin Sheng

[foodd]

Hello @TimHilverts and @MatthijsBonnema , this is a known issue (Issue #498), and is Tagged as ACTIVE.

WHERE TO LEARN MORE:

You can follow Issues at:  Power BI known issues - Power BI | Microsoft Learn

ISSUE DESCRIPTION:

Issue ID:  498

Date:  September 7, 2023

Title:  Export to CSV file truncated at 300 rows

Description: When you select Export data on a tabular visual's options menu and choose to export to a CSV file, the resulting downloaded file is truncated to 300 rows, rather than showing all the available rows.

Status:  Active

Reference URL:  https://learn.microsoft.com/en-us/power-bi/troubleshoot/known-issues/known-issue-498-export-csv-file...

ADDITIONAL SUGGESTIONS:

If you wish to close this thread and add a reply to the Issue #498 thread, you will be automatically

notified when it is resolved.

ADDITIONAL WORKAROUND:  Use DAX Studio to export data from selected Visual to CSV or Excel.

Additionally, you may use DAX Studio to export any table or data from a visual quite easily:

Using Performance analyzer you are able to capture the DAX query behind the visual.  Copy the DAX query, and use this in DAX Studio to return the data behind the visual.  This is also quite handy when writing documentation.

In this case, the DAX expression would be :

// DAX Query used by Table Visual to return Gross Sales column data
DEFINE
    VAR __DS0Core =
        DISTINCT ( 'financials'[Gross Sales] )
    VAR __DS0PrimaryWindowed =
        TOPN ( 501, __DS0Core, 'financials'[Gross Sales], 1 )

EVALUATE
__DS0PrimaryWindowed
ORDER BY 'financials'[Gross Sales]

Follow Gilbert Quevauvilliers post from June 2022 for general instructions.

[MatthijsBonnema]

We are facing exactly the same issue. It greatly influences our work flow for our local users. Could this be fixed ASAP?

Version: 2.121.644.0 (64 bits)