Paginated report Export to Excel fails but export to CSV works

[arunbyc]

When I try to export a Paginated Report (done usingReport Builder) to excel it fails with a message that it failed during rendering. Excel rendering extension: Argument not valid". Export to CSV worked . Export to excel failed with 275,000 rows as well as with 40 rows. The report has no unusual objects. No heading, no footer. Just five columns (text, numeric and date). Failed with the same message when I tried from the published report on Power BI service as well as from Report Builder. What should I do to troubleshoot?

Arun Rao

[Ray_Minds]

Answer :
There are some Troubleshooting step which we can follow 

1. Check for Hidden Columns or Conditional Visibility If your tablix has any rows or columns hidden by expressions
2. Validate the Data Type Mismatch - Invalid or mixed data types
3. Check for Hidden or Invalid Data Values, if one or more dataset fields might contain unexpected data.
4. Please validate the  report builder version . it might be impact due to old version as well

[v-ssriganesh]

Hi @arunbyc,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @Ritaf1983 for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

Thank you for being part of the Microsoft Fabric Community.

[Ritaf1983]

Hi @arunbyc 

This error usually comes from an Excel-renderer edge case in the layout, not from data size. Try the following:

1) disable CanShrink or set a minimum height for all textboxes (zero-height after shrink is a common cause)

2) make sure no items overlap inside the tablix when CanGrow kicks in

3) clear any custom number/date Format strings

4) avoid hiding columns by setting Width=0; use Hidden only

5) switch to a standard font and reasonable padding

6) ensure the tablix width does not exceed page width.
Test PDF/Word export; if they work and only Excel fails, it’s almost always a zero height/width or invalid format on a single textbox. Reduce the report until export succeeds to identify the offending column. CSV export is a valid temporary workaround.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[arunbyc]

Solved: It appears my report got corrupted. I created a new report and it now works (my previou attempts to create a new report failed because of a syntax error in my parameter definition. Once corrected, I am able to export the the new report to excel). But thanks for your valuable input. This helps me in the future if I run into these issues.

[v-ssriganesh]

Hello @arunbyc,
Thank you for your efforts. We are glad to know your issue has been resolved, and your experience will help other community members address similar challenges more effectively.

Best regards,
Ganesh Singamshetty.