View Performance Settings

The Default Cache Period is a setting for all reports that are based on the view. This field dictates how long  to store queried data in a cache so it may be reused by multiple report users. If the data in your source system is not time sensitive, you can set the cache time to be high and limit the impact of report users on the source system. The data is stored in a SQL data cache for the duration of the time you enter here.

This setting is entirely independent of the view's cache settings.

Set the maximum number of rows to be returned for any report written from this view. You can adjust this up or down depending on how long it takes for the rows to be returned.

When enabled, the report SQL that Yellowfin generates will include only the tables that are being used within the report, or are set to Mandatory.
For example, say a user creates a report with fields from table A and C, and table B is used to join A and C together. Yellowfin will include tables A, B, and C in the report query and will ignore any other tables in the view.

When toggled off, the report SQL that Yellowfin generates will include every table added to the view.

When enabled, this lets certain field types use the Filter Text Suggestions functionality with User Prompt filters. See Field Settings for more information.

When enabled, this option sets the Auto Refresh function in the Report Builder to be on by default.

This option sets the default for a similar toggle in the Report Builder for any new reports.

When enabled, this option sets the default for new reports created from this view to show duplicate records (ie, the Report Builder toggle is also enabled). 

When toggled off, this option sets the default for new reports created from this view to hide duplicate records (ie, the Report Builder toggle is toggled off).

Note: Toggling this option won’t affect existing reports, and the setting can also be overridden at the Report Builder level for each report.