Page History

Overview

Besides In addition to the UI configurations that Yellowfin has to offer, there are certain settings that you can alter using SQL.

To enforce a global language

configuration options within Yellowfin, a number of SQL-provoked settings exist, outlined below.

Enforce a global language

You can It is possible to use a hidden configuration to override the global language of a Yellowfin instance, but beware that this applies to all organizations within the instance — primary and clients alike. This forces Yellowfin to be translated into the specified language without any exceptions. To do so, add the following SQL into your configuration database:

INSERT INTO Configuration VALUES (1, "SYSTEM", "OVERRIDE_LANGUAGE", "zh_CN");

WhereIn this sample, “zh_CN” refers to the Java language locale code for the language you wish to enforce.

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

Disable URL title fetching 

This parameter prevents Yellowfin from fetching a URL title when sharing links in discussions. When set to TRUE, only the URL will be displayed in the discussion. When set to FALSE (or omitted, which is the default),  the title of the URL will be displayed in the discussion.

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

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

...

Conserve memory during export

To ensure that the memory does not get exhausted when exporting a large report to XLSX, you can enable a Low Memory Export option. This 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', 'ON');

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

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.

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 In the above code, set the <IP_org> to the IP of the client organization where you want this feature to be enabled. For example, replace this with 1 for the primary/default organization.

...

Disable outer join check

During the creation of views, you can configure outer joins to be treated as inner joins when creating View relationships in the database.

...

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(1, 'SYSTEM', 'DISABLEOUTERJOINCHECK', 'TRUE');

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

...

Conserve memory during report broadcast

Broadcast reports are run for each of the multiple recipients separately, taking into account their access filters, languages or other factors. However, to conserve memory usage and system performance, use the following configuration so that each recipient’s report is delivered as soon as it’s generated (instead of waiting for all the recipients’ reports to get done before sending them together).

...

INSERT INTO Configuration Values (1, 'SYSTEM', 'BROADCASTSENDINLINE', 'TRUE');

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

...

Enable carbon copy on broadcast emails

Enables the carbon copy option on broadcast emails, so multiple users who have access to the same data, are sent a single email which is sent to the first user, with the remaining recipients being sent a carbon copy. Note that all recipients will be visible to one another.

INSERT INTO Configuration Values (1, 'SYSTEM', 'COMBINEEMAILGROUPS', 'TRUE');

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

Disable row limit on filtered queries

...

Warning: Be careful when disabling the limit. If the filtered query returns a large amount number of values, it might result in a system hang uphang the system.

INSERT INTO Configuration Values (1, 'SYSTEM', 'DISABLEFILTERPROMPTLIMIT', 'TRUE');

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

Force Yellowfin to use legacy RC4 128 PDF encryption

When set to TRUE, this forces Yellowfin to use legacy RC4 128-bit encryption for PDFs rather than the default  of AES 256-bit encrypted PDFs.

Use the following SQL to do so:

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:

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