I'm using a Crystal Reports Web Viewer to display a CR report. It works perfectly fine in a CR Designer preview, however when I view it in a browser (any) the crosstab does not look as expected:
Specifically, column and row names have an additional margin added (values are displayed correctly) which cases the problem. I tried to change paragraph margin settings in my site's css file, but it doesn't make any difference. What could be causing this problem and how could this be solved?
When I change the specific p element margin property using Firebug, it displays correctly:
This is actually a Crystal Reports bug which affects 13.0.4 Version, it works fine when you run the same report using the 13.0.3 (and probably earlier) version. This bug is known to the CR team but won't be fixed till October (3 months to fix something that worked fine previously...): http://scn.sap.com/thread/3207181
Just love Crystal...
Related
As asked by few other members, on similar line, I want to have landscape orientation for only one of my subreport. I am using iReport 5.6.0 and JasperReports 5.6.0.
I searched and almost all solutions suggest to have 2 separate reports and add/append them programmatically as mentioned here.
This solution is probably not ideal for me as I have 4 dynamic subreports(can produce variable number of pages at run time) and I want only third subreport to be landscaped. So, at run time it will be difficult to identify the point to append my landscaped report.
Questions that I have:
Is this native feature now introduced in any new version of iReport to support different orientation of subreport?
If no inbuilt support in iReport, how can I programatically add
subreport in between, if I don't know at which location/page the subreport will be added.
I tried to look for a solution in JasperSoft Studio as well, but not success.
Thanks in advance.
Starting with JasperReports v6.0 you may achieve what you want with a Report Book. It is basically a report bundle where each report can have a different orientation.
But since Jaspersoft Studio(with version 5.5.0) became the official design client for JasperReports, you will not find this feature in iReport. So starting with Jaspersoft Studio v6.0 you will be able to use it.
Background:
Crystal reports 2008 prior. Now upgraded to crystal reports 2011
We have crystal reports version 14.0.2.364 installed to delivery reports to clients.
This problem appeared after the upgrade where someone gets a report delivered and the browser\crystal report viewer attempts to "auto-scroll" to a page automatically for you. Then some kind of issue causes it to scroll back to the previous page.
It continues to do this in a infinte loop where the browser\viewer never holds still long enough to do anything with the report.
Does anyone know how this has happened? (Again we have service pack 1 and 2 for the crystal reports 2011 package but I can find NOTHING on this problem anywhere).
Anyone else familiar with this problem or have seen this issue? (Happens in IE and Chrome btw)
UPDATE: It appears this problem is related purely to view size. If the view is set to 100 percent and with that view you can see the 2nd page, it starts to auto process the next page to display. So I tried a report that worked, and changed to view to 75% and the problem started up because that brought the 2nd page into view on the browser. This cannot possibly be how this is going to have to work (purely based on whether or not the second page is viewable based on local settings determines whether or not the browser\viewer goes into an infinite loop back and forth)
FINAL UPDATE (Resolution) : A setting in a web.xml file in the reporting services folder that instructs crystal report viewer to pre-render ALL pages of a report before viewing was the solution. Before this it was rendering ONLY the page the user was trying to view, hence if you have 2 pages in view it would infinitely loop in an attempt to display both pages. This setting was unfortunately buried in folders that are related to websphere which powers the application that runs our reports. It was called crystal_use_asynchronous_requests and we had to set it to true. Restarted websphere, and this resolved the issue
FINAL UPDATE (Resolution) : A setting in a web.xml file in the reporting services folder that instructs crystal report viewer to pre-render ALL pages of a report before viewing was the solution. Before this it was rendering ONLY the page the user was trying to view, hence if you have 2 pages in view it would infinitely loop in an attempt to display both pages. This setting was unfortunately buried in folders that are related to websphere which powers the application that runs our reports. It was called crystal_use_asynchronous_requests and we had to set it to true. Restarted websphere, and this resolved the issue
We have a problem when printing reports from within our application.
We want to avoid, that the print function in Crystal Reports 2008 scales reports automatically, so that the full report content fits into the printable area of the specific printer.
The predecessor Crystal reports 11 did not scale anything, that’s what we want to achieve for Crystal Reports 2008.
Sadly the following code throws an exception:
Dim layout As New CrystalDecisions.Shared.PrintLayoutSettings
'Disable scaling, does not work
layout.Scaling = PrintLayoutSettings.PrintScaling.DoNotScale
crystalReport.PrintToPrinter(printerSettings:=printerSettings,
pageSettings:=pageSettings,
reformatReportPageSettings:=False,
layoutSettings:=layout)
Interestingly the SAP Crystal Report Viewer 2008 prints reports correctly, without scaling, so we guess the functionality exists.
Have you tried this setting?
crystalReport.PrintOptions.DissociatePageSizeAndPrinterPaperSize
Have you tried setting this registry key?
HKEY_LOCAL_MACHINE\SOFTWARE\BusinessObjects\Suite12.0\CrystalReports\DesignerOptions
"DealWithMinimalMarginsWhenPrinting"="0"
From SAP forum. Did not work for us, but we are using CR for VS 2010.
According to this it might not be possible. The only workaround, we found so far, is to set your margins to printable area. Might not work for you.
In our case, we're using the custom paper size (8.27x8.75) and in crystal report viewer the scaling and centre settings were greyed out while set to True as described in the question above. By adding our custom paper size in the printer properties (customer paper) the problem has been fixed.
I created a simple grouping report using BIDS 2008 and have set the following properties of a textbox to hide a row in the Table (or Tablix) control.
CanGrow = false
CanShrink = true
Hidden = true
The report displays fine in Preview mode, however, when I deploy the reports to the server and view it, it doesn't render the same way. While the row remains hidden (I set it to an obnoxious color to see if would display on the server), there's a huge gap between the headers and the details in the report.
My question is, does the preview mode using a different rendering engine than the Reports Manager?
You can check the versions of bids being used locally and on your server to see if they are the same.
Visual Studio Help > About > Find SQL Server Reporting Services in the list and click on it. I currently have Version 10.50.1600.1
Report Manager In a browser open your http://[ServerName or Address]/Reportserver. At the bottom it will also have the version number, make sure these are the same, otherwise you could have varying results.
Also, the rendering engine is different for the viewer compared to print/PDF. A quick test would be to overlap some items on a report. In the viewer, the rendering engine will seperate these items so they are not touching, while print and PDF will leave them overlapped. This is just one of the differences I've noticed.
Yes, I believe the rendering engines are different.
In preview mode, have you turned on "Print Layout"? I have found that will give you a much more accurate idea of what the report will look like on the server.
Is this gap the same size as the textbox?
We are printing our Crystal Reports via the Crystal .NET API PrintToPrinter method. Recently it was discovered that when printing Cross Tab reports (reports that span multiple pages horizontally), only the first page is printed and the other "virtual" pages are not. We can preview the Reports fine in the .NET Crystal Report Viewer control and they show the wide report we expect, but when we print using the PrintToPrinter() method the output is definitely not what we just saw in that preview. Only the first page prints and you can see the beginning of what should be the second page cut off.
When printing through the Crystal Designer, the other pages are printed as expected. Also of note is that when we print via the "Print" button on the .NET Crystal Report Viewer control, it also prints all of the expected pages (they're jut not paged as well as when printing through the Crystal Designer).
Only the PrintToPrinter method (both overrides) seems to print only the first page of the Cross Tab Report.
I'm wondering if there's just setting I need to be setting programmatically to make this work or if I have just missed somewhere out there that this is a known issue with the Crystal .NET API?