This documentation corresponds to a historical version of Yellowfin

Icon

Access the latest release, or view a list of available versions of the documentation.

Skip to end of metadata
Go to start of metadata

Overview

Once you are editing a view you will be able to edit a number of options within the view.

View Options

Option

Description

Name

Provide a Business Name for the View, which will be used to identify it during the Report Building process.

Business Description

Provide a Business Description for the View, which will help the Report Writer understand the intended use and contents of the View.

Technical Description

Provide a Technical Description for the View, which will help Administrators understand the design and purpose of the View.

Audience

Provide an Audience Description to help identify who the View was designed for.

View Category

Select a View Category. View Categories define which Field Categories are available in the second step of the builder.

Performance

Option

Description

Default Cache Period (Hours)

Used to store queried data in a cache and reused by multiple report users. If the data in your source system is not time sensitive then you can set the cache time to be high and limit the impact of report users on the source system.

View Row Limit

You can set the maximum row to be returned for any report written from this view.

Optimise View

When enabled this will mean that Yellowfin will only include tables in report SQL 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.
If disabled, Yellowfin will include every table added to the View as part of the Report SQL.

Filter Text Suggestions

If enabled, this will allow certain fields to use the 'Filter Text Suggestions' functionality. See Field Access & Usage for more information.

View Security

Security on the view is used to set who has access to the view through the Report Builder, i.e. who can create/see reports based on the view. The three options available are:

Unsecure

All users with functional access to the database can write reports against this view.

Edit restricted

Only defined users will be able to create a report using this view. All other users will be able to read the reports that have been created by authorised users.

Restricted

Only defined users can read and/or write reports from data in this view.

Note: these options do not control who can edit the view itself, they only control the Report Builder access to the view.

Assigning Security

  1. Once you have selected the ‘secure’ option from the view option the security management step will be displayed.
  2. You will need to search for which users or groups require access. Click the search link and select the user or group required.
  3. Select the appropriate access level.
  4. Click the add button to add them to the access list. You can add as many users or groups as users to the list as appropriate.



  • No labels