Changes

Jump to: navigation, search

Reports

2,414 bytes added, 17:59, 2 July 2019
no edit summary
|-
||'''Criteria Text'''
||Text used to prompt the [[user]] when they are [[Prompting for Criteria in Reports|required to enter]] some [[Criteria|criteria]] values. This setting will also specify the introduction text, as well as labels for [[Custom Fields]]. Labels are defined by a hyphen (-) preceding the label ('''ex: '''"-First Name") and are applied to the criteria fields in the other that they are entered.
|-
||'''View Mode'''
{| class="wikitable"
|-
||'''Report Caching'''
||
'''Report Caching Options: Enable -'''
||'''Caching Options: Cache By User Enable - '''Enabling caching is a useful function that can help improve loading time and reduce the processing load on the server. This function is best for complex reports and reports that are accessed regularly. 
* '''Do not '''enable general caching for reports that [[Prompting for Criteria in Reports|prompt the user for criteria]].  '''Caching Options: Cache By User - '''Caching by user'' must be used for'' when a report includes [[:Category:Criteria|criteria]] to filter based on the user that opens the report (i.e. =@userid@).  '''Cache Life Span - '''Enter an appropriate cache life span in minutes. Therefore, rather than re-creating the report each time it is run, caching stores the results for the duration specified in this field. The first time a report is viewed, it will be created by querying the database and live data will be displayed. Anyone viewing the report after this and ''within ''the life span will see a snapshot of the report from the cache.  * Changes to underlying data will not be reflected in the report during the '''Cache Life Span. '''* The report will be updated only once the life span has expired. * In general, [[Building Sub-Reports|Sub-Reports]] should not be cached, though the parent report can be cached if appropriate. 
|-
||'''[[Field Caching]]'''
||
'''Frequency - '''The frequency of field caching (what is also referred to as '''[[S''''''cheduled Reports]]''') can be set as follows: * '''''Disabled: '''''Default setting; indicates a report will not run on an automated schedule* '''''Daily: '''''The report will run every morning. * '''''Weekly: '''''The report will run every Sunday.* '''''Monthly: '''''The report will run on the first of every month. 
'''Identifier Column - '''Select a report column from those available in the [[Report Builder]] that will uniquely identify the record to update. This is the ''match field ''as it indicates the field that allows the system to know which record to update. 
'''Column Field Value Column - '''Select a report column from those available in the [[Report Builder]] for the data that you wish to store; this acts as a ''source field ''as the setting represents the values that the system will use to update the '''Custom Field '''specified in the next field. 
'''Custom Field - '''Select a dataset-specific [[Custom Field]] to where the dataset will be stored. This is the ''destination field ''as the custom field will be updated each time that the report is run. 
'''Last Run - '''This will display a date and time stamp of the last time that the field caching/scheduled report was run. 
|}
2,299
edits

Navigation menu