Caching option - Revision history

Crmtogether at 12:20, 10 July 2015

2015-07-10T12:20:10Z

← Older revision		Revision as of 13:20, 10 July 2015
Line 5:		Line 5:
	For example if you have a report that takes 1 minute to run (maybe with some complex SQL command) as the web is stateless any interaction with the report (drill down for example) that posts back to the server will re-run that command. This would make the report unusable so to assist with that we have a caching option (off by default) in the system.		For example if you have a report that takes 1 minute to run (maybe with some complex SQL command) as the web is stateless any interaction with the report (drill down for example) that posts back to the server will re-run that command. This would make the report unusable so to assist with that we have a caching option (off by default) in the system.

	The configuration option is		The configuration option (in custompages/crviewer/web.config) is

	<add key="UseCaching" value="N" />		<add key="UseCaching" value="N" />

Crmtogether at 14:22, 5 January 2015

2015-01-05T14:22:42Z

← Older revision		Revision as of 15:22, 5 January 2015
Line 1:		Line 1:
	*~~part~~ of new update out ~~Dec 2014~~		* Part of new update out Jan 2015

	Whilst typically you would not deliver large complex reports over the web there are instances where it is needed.		Whilst typically you would not deliver large complex reports over the web there are instances where it is needed.

Crmtogether at 15:27, 1 December 2014

2014-12-01T15:27:20Z

← Older revision		Revision as of 16:27, 1 December 2014
Line 1:		Line 1:
	*part of new update out Dec ~~2015~~		*part of new update out Dec 2014

	Whilst typically you would not deliver large complex reports over the web there are instances where it is needed.		Whilst typically you would not deliver large complex reports over the web there are instances where it is needed.

Crmtogether at 09:40, 27 November 2014

2014-11-27T09:40:21Z

← Older revision		Revision as of 10:40, 27 November 2014
Line 17:		Line 17:
	Files remain in use for up to one hour and are deleted by the system after 24 hours.		Files remain in use for up to one hour and are deleted by the system after 24 hours.

	Ideally we recommend that you do not use this but instead follow the [http://crystalmanager.crmtogether.com/index.php?title=Recommendations Recommendations ]		Ideally we recommend that you do not use this but instead follow the Report Writer [http://crystalmanager.crmtogether.com/index.php?title=Recommendations Recommendations ]

Crmtogether at 09:39, 27 November 2014

2014-11-27T09:39:55Z

← Older revision		Revision as of 10:39, 27 November 2014
Line 17:		Line 17:
	Files remain in use for up to one hour and are deleted by the system after 24 hours.		Files remain in use for up to one hour and are deleted by the system after 24 hours.

	Ideally we recommend that you do not use this but instead follow the [~~Recommendations~~ http://crystalmanager.crmtogether.com/index.php?title=Recommendations]		Ideally we recommend that you do not use this but instead follow the [http://crystalmanager.crmtogether.com/index.php?title=Recommendations Recommendations ]

Crmtogether: Created page with "*part of new update out Dec 2015 Whilst typically you would not deliver large complex reports over the web there are instances where it is needed. For example if you have a..."

2014-11-27T09:39:38Z

Created page with "*part of new update out Dec 2015 Whilst typically you would not deliver large complex reports over the web there are instances where it is needed. For example if you have a..."

New page

*part of new update out Dec 2015

Whilst typically you would not deliver large complex reports over the web there are instances where it is needed.

For example if you have a report that takes 1 minute to run (maybe with some complex SQL command) as the web is stateless any interaction with the report (drill down for example) that posts back to the server will re-run that command. This would make the report unusable so to assist with that we have a caching option (off by default) in the system.

The configuration option is

<add key="UseCaching" value="N" />

You set this to be

<add key="UseCaching" value="Y" />

This will create a "cache" folder and store any reports created in here with the name and parameters. Then when the same report is requested with the same parameters the saved version of the report (with the data already in it) will be returned.

Files remain in use for up to one hour and are deleted by the system after 24 hours.

Ideally we recommend that you do not use this but instead follow the [Recommendations http://crystalmanager.crmtogether.com/index.php?title=Recommendations]