A SSRS 2005 report that is run by multiple users is generating about 45,000+ records and then being exported to Excel. This is working fine, but when the users try to sort/filter the results they are seeing a huge amount of lag. At first I thought that it was just because of the large number of rows, but we found that when we stripped all of the formatting from the Excel file the report sorted and filtered quickly. Is this a common problem any of you have seen and how would you resolve it? They need the formatting to stay on the main report, so if I could somehow export without formatting that would be ideal.
Thanks!
There are only three settings you can set for the ReportViewer excel renderer.
See Excel Device Info
Unfortunately, none of which will omit formatting in your exported report.
The only thing I can suggest is that you strip out all the formatting from the RDLC report file, prior to exporting.
Related
MS Excel deleting the 0’s in the excel download of the report in OBIEE.
I have one primary id which has data like 001,002,003
The column is varchar and is treated as string in the report but when I export that to excel I'm getting 1,2,3.But I need the data should be like 001,002,003 only even after export.
I think excel is thinking this is number so it is cutting off zeros.
The user want to see data in excel exactly how it is displaying in report.
Any suggestion would be helpful.
You're sadly not specifying on which exact version this happens. The problem is definitely Excel and since this is a known issue, Oracle introduced a setting in OBIEE some years back. It lets you define whether to transfer raw data to Excel (as above where Excel then messes it up) or formatted, in which case your string stays a string.
In the instanceconfig.xml you can set the following:
UseFormattedValue
When you set that to UseFormattedValue, Execl is forced to accept the actual formatting. Not what Excel thinks the data is.
The other setting is UseRawValue.
I have quite a complex SSRS report that I would like to export to Excel more or less how it looks in the web output.
Export to Excel and opening in Excel 2010 yields the following error:
Excel was able to open the file by repairing or removing the unreadable content.
Removed part: /xl/styles.xml part (Styles)
All the styling is gone from the report, so it looks terrible.
After isolation testing it I have fixed 99% of the style errors by one simple change:
Excel doesn't seem to like 'Total' cells for Row Groups within tables having no Font='' (these cells are auto-created when you create a total for a group)
Font=", 10pt, Default, Bold, Default"
Change Font to "Arial":
Font="Arial, 10pt, Default, Bold, Default"
Another thing to look for if all of your textboxes have a font name is the Format Property. I had a date field that I wanted formatted, so, in the Format field, I used =Format(Fields!CreatedDate.Value, "MM/dd/yyyy"). This worked when viewing the report, however, when exporting, received the unreadable content error. I eventually just used: MM/dd/yyyy in the format property, that solved my problem.
In my case, I fixed this by preventing a divide-by-zero.
For some weird reason, instead of failing to render a divide-by-zero, it displays the word Infinity.
I have a report that is run on SSRS and the numbers / everything looks good. I have the data in a table w/ some grouping / drilldown capability.
My issue is that when I export to Excel, and I open up my groups....there is an extra line! My summary data is the same from SSRS, but now it looks wrong because there is an extra row.
Regardless of what is in the database....shouldn't the results always be the same? Has anyone ever encountered this before?
I am using SSRS 2008R2
The results may not always be the same because the rendering extension was not created to cover many different situations and reporting designs.
However, with your situation, make sure you have no overlapping controls, rows, other text-boxes etc.
I have a report where I have 50+ fields and I am exporting this report from crystal to excel. Once in excel the data columns are the proper width but the headings are truncated. Is there a way to get the headings to dynamically expand like the data does?
Have you tried using the grid line tools to line up all your columns and headers? Ensure snap to grid is on and that all headers/fields are the same size on screen.
Basically you want the crystal report in the designer to look similar to an excel report; with all the headers and fields in a grid like structure.
Crystal also produced a document many moons ago when they were owned by Seagate describing how to avoid formatting problems when exporting to excel. Check it out HERE
This helped me a load when I had to build stock reports and summaries for one of my customers.
I am working on an excel report in CrystalReports, in VS2005. I have a field in the Details section which can have up to 255 characters of text, and I want the height of the row in excel to expand so that the entire text can be seen initially when the report is generated.
I set CanGrow=True in the field's properties, and the field does seem to grow; the field is only one line (Height=159), but many of the rows display multiple, wrapped lines of text. Some rows intermittently have the bottem half of the last line of text cut off; the user has to expand the row a little bit to see it. There doesn't seem to be a particular field length that causes this - in one case, it has four lines total in the output, and in another case, it has only three.
Can anyone suggest what might be the cause of this, or how I could work around it?
Thanks in advance for any help you guys can offer.
[Edit: I am no longer working on this project, so I never found out what became of this setting. Most likely it wasn't fixed, since it's not a critical issue.]
One solution to this issue that I've come up with in the past is to have two separate reports. One for display and exporting to pdfor rtf and another report for exporting to Excel.
I know in general this is not a good approach because there is the possibility for data to be different in the export than the display report, but if careful it works well.
I have a situation where a client needs data printed in a specific format on a report, but there is way to much data to physically be able to fit on a page. We worked out a solution that I run a "display version" of the report that fits most of the data, but the rest of the data necessary for there client is added only to the "Excel version" of the report.
To do this I simply load the "display report" to the report viewer as you normally would, but when you go to export the report I load the "excel report" with the same parameters as the "display report" and call the code to export the data to Excel.
By using this method the "display report" can be formatted any way necessary without having to worry about messing up the export to excel. The excel report fields can then be made a smaller size than required by the display report because the data should export even regardless of the size of the field. Doing this allows you to fit more data on the Excel export report.
Since both reports use the same datasource you will have an issue if you make a change that you have to remember to go verify the database on each report to see the new database changes, but this method allows you to include more data and in a different format than the display version of the report.
Hope this helps.
While not a solution for Crystal (I don't know of one), as part of the reporting team at GrapeCity-Data Dynamics, we've worked with similar issues taking free-form reports to excel spreadsheets for a decade. In our Data Dynamics Reports product we came up with a completely new way of solving the problem of exporting reports to excel.
We allow you to create a template for the report output. The template is a basic excel file with place holders for the various textboxes (or other controls) and regions (tables, lists, etc.) in the report. You can open this template inside of excel and modify the properties of the cells and rows. In the scenario you describe, you can export a "template" from Data Dynamics Reports and then modify the autosize property of the row in the template containing the placeholder for the textbox you're struggling with.
When you export the report to excel next time, just specify the template to Data Dynamics Reports (which can be done programmatically and transparently to the end user) and Data Dynamics Reports will honor all settings you specified in the template.
This is hard to explain so there is a ~2 minute screencast that shows this feature at our website in the following location:
http://www.datadynamics.com/Products/DDRPT/ScreencastViewer.aspx?ID=XLS01
For more information about the product and for a free trial download visit: http://www.datadynamics.com/DataDynamicsReports
Scott Willeke
GrapeCity - Data Dynamics