Recommendations - Revision history

Crmtogether at 09:31, 27 November 2014

2014-11-27T09:31:48Z

← Older revision		Revision as of 10:31, 27 November 2014
Line 4:		Line 4:

	Recommendations for Optimizing your Reports		Recommendations for Optimizing your Reports
	Ref:
			Ref: [https://www.google.ie/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CCIQFjAA&url=http%3A%2F%2Fhelp.sap.com%2Fbusinessobject%2Fproduct_guides%2FsapCRVS2010%2Fen%2Fcrnet10_dg_en.pdf&ei=bu92VMvjKcaz7ga3i4C4Cw&usg=AFQjCNHRmxT9iBWvBJepf5uVxzKgrUi88Q&bvm=bv.80642063,d.ZGU]

	1. Use Smaller Reports		1. Use Smaller Reports

Crmtogether at 09:31, 27 November 2014

2014-11-27T09:31:11Z

← Older revision		Revision as of 10:31, 27 November 2014
Line 7:		Line 7:

	1. Use Smaller Reports		1. Use Smaller Reports
	When possible, keep your reports to less than 15 pages.In Web applications, users often want to see only a few key pieces of data rather than pages and pages of data.		When possible, keep your reports to less than 15 pages.
			In Web applications, users often want to see only a few key pieces of data rather than pages and pages of data.

	2. Use Smaller Graphics		2. Use Smaller Graphics
	When a report is displayed in a CrystalReportViewer control and the report contains a graphic (a chart or an image), the report engine must create a temporary JPG file (in the dynamic_images folder) and the browser must make a separate request to the Web server to retrieve it		When a report is displayed in a CrystalReportViewer control and the report contains a graphic (a chart or an image),
			the report engine must create a temporary JPG file (in the dynamic_images folder) and
			the browser must make a separate request to the Web server to retrieve it

	3. Redesign Subreports to Reduce Demand		3. Redesign Subreports to Reduce Demand
	While subreports can often be used to create complex reports, they add considerable overhead. This doesn't mean that subreports shouldn't be used, but they should be used sparingly.		While subreports can often be used to create complex reports, they add considerable overhead. This doesn't mean that subreports shouldn't be used,
	Also consider that when subreports are placed in sections that are repeated, such as group headers or the details section, each instance of that subreport requires its own report job. This means that a 100-record report with a subreport in the details section actually runs 101 report jobs.		but they should be used sparingly.
			Also consider that when subreports are placed in sections that are repeated, such as group headers or the details section,
			each instance of that subreport requires its own report job. This means that a 100-record report with a subreport in the details section actually runs 101 report jobs.

	4. Don't Use Fields that Block On-demand Processing		4. Don't Use Fields that Block On-demand Processing
	SAP Crystal Reports processes reports on-demand. For example, if the first page of a report is to be displayed, it only processes that first page, not the whole report. However, inserting fields or formulas onto the first page of a report that depend upon the completion of the report processing prevents on-demand processing. For example, if the "Page N of M" special field is placed on the first page, the entire report must be processed to determine the page count before this field can be rendered. This causes the first page to wait until the whole report was finished processing before it can be displayed. The same behavior occurs when you use a percentage of summary calculations. Consider not using these types of fields		SAP Crystal Reports processes reports on-demand. For example, if the first page of a report is to be displayed,
			it only processes that first page, not the whole report. However, inserting fields or formulas onto the first page of a report
			that depend upon the completion of the report processing prevents on-demand processing. For example,
			if the "Page N of M" special field is placed on the first page, the entire report must be processed to determine the page
			count before this field can be rendered. This causes the first page to wait until the whole report was finished processing
			before it can be displayed. The same behavior occurs when you use a percentage of summary calculations.
			Consider not using these types of fields

	5. Select the No Printer Option Under Print Setup		5. Select the No Printer Option Under Print Setup

Crmtogether: Created page with " As the web is stateless the reports will behave differently to that on a desktop. Any report requests will re-run any and all queries run when first opened. *See new caching..."

2014-11-27T09:15:37Z

Created page with " As the web is stateless the reports will behave differently to that on a desktop. Any report requests will re-run any and all queries run when first opened. *See new caching..."

New page

As the web is stateless the reports will behave differently to that on a desktop. Any report requests will re-run any and all queries run when first opened.
*See new caching option for alternative to this

Recommendations for Optimizing your Reports
Ref:

1. Use Smaller Reports
When possible, keep your reports to less than 15 pages.In Web applications, users often want to see only a few key pieces of data rather than pages and pages of data.

2. Use Smaller Graphics
When a report is displayed in a CrystalReportViewer control and the report contains a graphic (a chart or an image), the report engine must create a temporary JPG file (in the dynamic_images folder) and the browser must make a separate request to the Web server to retrieve it

3. Redesign Subreports to Reduce Demand
While subreports can often be used to create complex reports, they add considerable overhead. This doesn't mean that subreports shouldn't be used, but they should be used sparingly.
Also consider that when subreports are placed in sections that are repeated, such as group headers or the details section, each instance of that subreport requires its own report job. This means that a 100-record report with a subreport in the details section actually runs 101 report jobs.

4. Don't Use Fields that Block On-demand Processing
SAP Crystal Reports processes reports on-demand. For example, if the first page of a report is to be displayed, it only processes that first page, not the whole report. However, inserting fields or formulas onto the first page of a report that depend upon the completion of the report processing prevents on-demand processing. For example, if the "Page N of M" special field is placed on the first page, the entire report must be processed to determine the page count before this field can be rendered. This causes the first page to wait until the whole report was finished processing before it can be displayed. The same behavior occurs when you use a percentage of summary calculations. Consider not using these types of fields

5. Select the No Printer Option Under Print Setup