The company I'm working for has an older version of Crystal Reports before it was part of SAP, it was part of buinessobjects. We have version 11.5 of crystal reports businessobjects.
I am running into a unique issue with one report. When I schedule the report to run on a weekly basis, it adds an attachement Excel document. The issue is that the headers are missing. I have checked off the option to include headers in the attachment, but it is still not showing up.
I'm not sure why this is, because when I run the report directly in Crystal Reports, it shows the headers and I'm able to export it as an excel (data only) from Crystal Reports and the headers come accross.
It is only when I schedule the report to run it does not give the headers. I have tried all the options I can think of and done research, but the version my company is running is so old, that it is hard to find information on how to do things.
Thanks,
Dave
Are you exporting in Excel Data Only ?
When you export to Excel (Data Only), under the Excel Format Options, choose Custom.
Expand the Options.
Ensure to uncheck Simplify page headers
Related
I made a change to a report today that displays some financial data - it was being displayed incorrectly so I made a change to ensure it displays the correct data.
In Visual Studio the data is now correct when I run the ssrs report but when I import the report into CRM 2011 the data is still showing incorrectly as it did before.
I have checked and rechecked that the report is pointing at the same database in both instances.
I have tried everything I can think of:
Removing the field and then re-adding it
Changing the name of the field
Removing hyperlinks that were in the report
Removing a child report that was linked to the report
Any ideas what else I can try?
Really sorry to bother everybody!
It was a date issue - my local PC date is set to UK date whereas for some reason our CRM database is set to US date.
When I am exporting my crystal report on asp.net, the gridlines are not showing on Excel, on PDF, it works perfectly fine.
Is there any way to correct this problem? I tried putting border color to the fields but it is very tedious.
Thanks in advance.
I am using Crystal Report Viewer 10 on Visual Studio 2012
After searching for the answer for this, I have found out that there is no crystal Report Version that is able to export a line or box in Excel, therefore gridlines is not appearing,
WORKAROUND: use the field border by formating it manually
However, having this an important function in any reporting tools, we can suggest this to SAP for it to be considered in their updates on their future releases of the product
JUST GO TO THIS PAGE AND HAVE A VOTE UP FOR THE IDEA.
https://ideas.sap.com/SAPCrystalReports/D27006#comments (5 VOTES CURRENTLY)
and
https://ideas.sap.com/ct/ct_a_view_idea.bix?c=A5E8DEA8-D886-4250-BA2B-039F7D32FFC0&idea_id=776FEC64-B932-4159-8C31-759613225B0C (9 votes)
THEY NEED TO HAVE AT LEAST 20 VOTES
On a daily basis we need to export Excel sheets (showing tables + charts) with then current SSAS data and copy the sheets into specific SharePoint document folders. I guess moving the sheets to SharePoint is the smaller task, since the folder can be used like a windows directory. I am uncertain about how to do the rest. I considered:
1) SSRS, schedule the export via Server Agent somehow (I guess this is possible since reports can be exported to Excel so the automated export is probably doable without jumping through too many loops).
2) Design the report in Excel instead (with pivot tables + charts), put this as a template into a Sharepoint library and somehow make the sheet update from the Data Source and export it into a static (not connected) sheet on a daily basis.
While I am quiet sure that 1) is doable I am totally unsure about 2), but 2) has the valuable benefit that the domain expert can make up the sheet without having to install and mess with the Report Designer.
I am thankful for any comment about approach 1 or 2 or any alternative.
If you go with your option 1, consider setting up an email enabled SharePoint list and setting up a subscription in SSRS to email the Excel reports to that list.
For the email enabled list see
http://office.microsoft.com/en-us/windows-sharepoint-services-help/add-content-to-sites-by-sending-e-mail-HA010086730.aspx
For the SSRS subscription see
http://msdn.microsoft.com/en-us/library/ms159762.aspx
It does have the drawback that your subject matter experts might have to learn ReportBuilder, but if they can learn Excel then ReportBuilder shouldn't be too much of a stretch. If you do get option 2 working, though, post back, it sounds interesting.
We have a report that queries Oracle and uses Crystal Reports to make a report. The users would like the output as both a Crystal Report and Excel. Yes, I know they can output the results of the report to Excel. Is there any (reasonable) way to automatically provide both output formats? The reports are run in Business Objects Enterprise.
I see the output format is set in the BOE Central Managament Console for the report under Schedule/Format. That makes it look like the option is one or the other, not both.
You can create a new publication and add this report, it will allow you to have both crystal report and excel formats on the email as attachments in BOE. Hope this helps.
Regards
Tracey
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