Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
RLSmart
Helper I
Helper I

Export to Excel ,even small number of rows, not exporting completely

Hi, I'm using PBIRS, and my users access reports via our Reporting Services portal. 

I have a report with a small number of rows that the users need to dump to excel for reconciliation with another system.  

This is a case where many users need access to this data, but cannot all have access to a vendor's site, so we pull the file in and let them access it via RS.  The report is just a straight table, no aggregation, in fact, no measures at all in the dataset.  There are no filters, even.

Today's file contains 1348 rows, but when I export the table to excel, it only exports 981 of the rows.    We get the same results, whether we choose excel or csv.  

 

We are not anywhere near the limit, so what is happening here?  

 

ETA: The data source is a single table, and the model contains a single table so there is no filtering via join either.  Doesn't even have a date table.  

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @RLSmart ,

 

Check whether you have reached the limitation of "exporting data to excel":

https://docs.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-export-data#limitations-and...

 

 
Best Regards,
Kelly
Did I answer your question? Mark my post as a solution!

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Thanks @Anonymous. 

 

For those looking for a quick solution -> If you are using a SQL view as source for a table, then its most likely because a unique Id column is not there.  Have tested the export feature and found:

 

 - For tables with regular primary key cols, like identity(1,1) ->  export works fine with or without the id col being in the table (haven't tested with summarization/count/sum/etc.) on the report.

 

-  For tables using SQL views -> Export only works fine when you have a unique col within the table on the report.  In my case using newID() to generate a GUID id col worked fine. 

 

Otherwise, you will have to refer to the link shared by @Anonymous  to pinpoint what could be your issue.

Anonymous
Not applicable

Hi @RLSmart ,

 

Check whether you have reached the limitation of "exporting data to excel":

https://docs.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-export-data#limitations-and...

 

 
Best Regards,
Kelly
Did I answer your question? Mark my post as a solution!

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors