Export Data - Data Exceeds the Limit

[ovetteabejuela]

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?

[v-yuezhe-msft]

@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,
Lydia

[ovetteabejuela]

Thank 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.

[v-yuezhe-msft]

@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

[alex139]

@ovetteabejuela

As a temporary workaround, you can try reverting to the October version or you can ignore the warning for datasets smaller than 30k rows.

[ovetteabejuela]

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.

[alex139]

@ovetteabejuela

I will test this tomorrow morning. If you have any datasets you have used in your tests please share. Thank you.

[v-yuezhe-msft]

@ovetteabejuela,

The fix of this issue will be released on January.

Regards,
Lydia

[ovetteabejuela]

@v-yuezhe-msft,

Looking forward for the fix, thank you.

[AfriKan]

Thanks for raising this issue.  I have the same problem and look forward to the Jan '18 solution