Page History

Overview

In addition to the UI configuration options within Yellowfin, a number of SQL-provoked settings exist, outlined below.

...

Also in this sample, 1 denotes the primary/default organization. This is a system-wide setting that cannot be enabled for specific client organizations; Thereforetherefore, this value must always be set to 1.

...

The console should display some empty components for the serverInfo object, apart from the base and loaded resources values (required by the browser).

Limit cached filter context

Use this parameter to force the filter formatting options 'Ignore Report Filters when Loading Cached Value' and 'Restrict SQL Context to Filter Columns Only' on (see the Dimension filter settings table of events on this page for more info). 

When set to FALSE (default), these two options are displayed within the UI and the user can choose whether toggle them on or off.

When set to TRUE, these two options are both forced to be enabled on all filters on all reports on all datasources, and the options within the UI are hidden from display. In this situation, users don't need to remember to switch these settings on, and the only way they can be switched off is by changing this advanced configuration from TRUE to FALSE.

INSERT INTO Configuration(1, 'SYSTEM', 'LIMITCACHEDFILTERCONTEXT', 'TRUE');

In this sample, 1 signifies the primary/default organization.

Prevent data sources from being flagged as "unavailable" even when offline

When Yellowfin flags a data source as unavailable, it relies on a web service call or a Yellowfin administrator to manually bring it back online by accessing the list of data sources in the Admin Console, finding the data source flagged as offline, and clicking on the Test Connection button — even if a data source has come back online independently. In some situations where data sources are only offline temporarily, you may wish to avoid them being flagged as unavailable to reduce manual intervention. In this case, you can use parameter to prevent any flagging.

When set to FALSE (default), if a data source is detected to be offline, it will be flagged as unavailable and will require manual intervention to come back online.

When set to TRUE, none of your data sources will be flagged as unavailable, whether they're offline temporarily or permanently. You would need to manually investigate each data source independently of Yellowfin.

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'NEVERMARKSOURCEUNAVAILABLE', 'true');

This is a system-wide setting that cannot be enabled for specific client organizations; therefore, this value must always be set to 1.

Oracle scope selector

This configuration option can reduce the scope for Yellowfin to use when fetching synonym objects from an Oracle data source. 

When this option is not used, Yellowfin fetches ALL_OBJECTS and ALL_SYNONYMS

When the value of this configuration is "USER", Yellowfin fetches USER_OBJECTS and USER_SYNONYMS to improve performance.

INSERT INTO Configuration VALUES(1,'SYSTEM', 'ORCL_SCOPE','USER');

This is a system-wide setting that cannot be enabled for specific client organizations; therefore, this value must always be set to 1.

Allow empty or null value to be used for cached filter

Use this parameter to get parent filter results to persist when a child filter result contains empty or null values.

When set to FALSE (default), cached filters will ignore empty or null values.

When set to TRUE, cached filters will not ignore empty or null values.

INSERT INTO Configuration values(1, 'SYSTEM', 'ALLOWNULLCACHEFILTERS', 'TRUE');

In this sample, 1 signifies the primary/default organization.. Anchorlowmemoryexportlowmemoryexport

Disable URL title fetching 

...

Conserve memory during export

To ensure that the memory does not get The low memory export configuration prevents memory from being exhausted when exporting a large report reports to XLSX , you can enable the Low Memory Export option. This format. When the configuration is enabled, the system processes reports in parts in memory, rather than as a whole.

To enable this feature, add the following SQL code into your configuration database:

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(<IP_org>, 'SYSTEM', 'REPORTLOWMEMORYEXPORT', 'ONTRUE');

Remember to set your value for <IP_org> to either the primary org (1) or a client org.

Display Low Memory Exports toggle

This configuration displays the Low Memory Exports toggle option on the report Export Settings dialog box, providing the option to enable or disable the feature within the UI per report. The toggle is also displayed on the System Configuration page to enable or disable the feature as the default setting for all report exports.

Enabling this option overrides the global setting, REPORTLOWMEMORYEXPORT which enforces low memory exports. This means exports will be faster, but more memory-intensive.

When set to TRUE, the export option ‘Low Memory Exports’ is displayed in the report Export Settings dialog box. 

To enable this feature, add the following SQL code into your configuration database:

INSERT INTO Configuration VALUES (<IP_org>, 'SYSTEM', 'SHOWLOWMEMORYEXPORTOPTION', 'TRUE');

Remember to set your value for <IP_org> to either the primary org (1) or a client org.

...

In this sample, 1 signifies the primary/default organization.

Log failed login events

When set to FALSE (default), only failed login attempts made via a valid username are recorded in the system log files. 

When set to TRUE, all failed login attempts to Yellowfin are recorded in the system logs, whether the username is valid or not, allowing for more accurate auditing of login activity.

Use the following SQL to do so:

INSERT INTO Configuration VALUES (1,'SYSTEM', 'LOGFAILEDLOGINEVENTDETAILSENABLED','TRUE')

In this sample, 1 signifies the primary/default organization.

Broadcast filename template

This configuration can be used as a template for filenames used in email broadcasts, FTP schedules and save to disk schedules. When set, it applies to all broadcasts on your Yellowfin instance. This configuration overrides the Append Broadcast Date and Append Broadcast Time options, therefore their respective checkboxes will no longer appear on the broadcast configuration dialog box once this configuration is set.

The value stored in the configuration can contain placeholders for the report name and date that will be filled in by the broadcast process:

• The {filename} placeholder will be replaced with the report name for email broadcasts, or the file name specified in the FTP Broadcast and Save to Disk Schedule dialog boxes.
• All other placeholders within the curly brackets are treated as datetime format strings, following the SimpleDateFormat specification.

For example, utilizing the Broadcast Filename Template format {yyyy-MM-dd_HH-mm-ss} as outlined in the code snippet below, will produce the filename ‘Ski Report - 2020-01-01_12-34-56.pdf’. 

The resulting filename must be compatible with the filesystem if FTP schedules and Save to Disk schedules are used. For example, if the destination FTP server or the Yellowfin instance are running on Windows, then using a colon character (:) should be avoided as it is an illegal character in filenames on NTFS. Email broadcasts, however, will replace illegal characters in filenames with underscores.

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'BROADCASTFILENAMETEMPLATE', '{filename} - {yyyy-MM-dd_HH-mm-ss}');

In this sample, 1 denotes the primary/default organization. This is a system-wide setting that cannot be enabled for specific client organizations; therefore, this value must always be set to 1.

Enabling JNDI data source connections

JNDI data source connection types can be enabled by running the following SQL against your configuration database: INSERT INTO Configuration(1, 'SYSTEM', 'JNDISOURCEENABLED', 'TRUE');

Enable non-mandatory filters on Jasper Reports

Use the following code to enable non-mandatory filters on Jasper Reports.

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'JASPERFILTERSNOTMANDATORY', 'true');

Limit the number of unique rows for cross-tab and other similar reports

You can enable the maximum number of unique rows that can be generated for cross-tab reports and certain chart types to avoid memory exhaustion.

INSERT INTO Configuration VALUES (1, "SYSTEM", "CELL_LIMIT", "80000");

"80000" is an example of the limit only, please change it to suit your needs.

Set a default broadcast format

Use the following configuration to set a default format for broadcasts.

INSERT INTO Configuration (iporg, configtypecode, configcode, configdata) 
VALUES (1, 'SYSTEM', 'BROADCASTDEFAULTCODE', 'XLSX');

XLSX is an example of the format. You can choose from the following formats: 'HTML', 'CSV', 'DOCX', 'PDF', 'LINK', 'XLSX, 'TXT'.

Restrict guest users from being redirected to the Browse page

The following configuration can be used to limit guest users from being directed to the Browse page when canceling a report, thus not allowing the user to see all public reports.

RESTRICTGUESTUSER = TRUE

The default would be false, and still allow exit to the Browse page. Setting to TRUE would redirect users to a “Not available” page.

Prevent license refreshes when deleting users

The following configuration can be used to prevent License Refreshes from cascading across the cluster upon user deletion. This approach serves as an alternative to a bulk delete web service that could efficiently delete multiple users with just one license refresh.

INSERT INTO Configuration VALUES (1, "SYSTEM", "SKIPUSERDELETELICENCEREFRESH", "TRUE");