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.

Hide JS API details

You can hide the Java version and OS version from the JS API response by setting HIDEJSAPIDETAILS. to true. In this case, the following components of the serverInfo object 

javaVersion, operatingSystem, opertatingSystemArch, operatingSystemVersion, releaseVersion, schemaVersion, subVersion, buildVersion

Note: This will not hide the base and loaded resources values because they are always required by the browser to load further parts of the JS API. 

To make use of this option, start by running this SQL on your database (this is a system-wide setting, so the IP Org is set to 1):

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(1, 'SYSTEM', 'HIDEJSPAPIDETAILS', 'true');

Next, restart your Yellowfin instance, then embed a piece of content from the JS API. It doesn't matter what it is; you just need to load the JS API. You could even do this with the basic script tag:

<script src="http://yourYfServer/JsAPI/v3"></script>

To test this has worked, open your browser console and type: 

yellowfin.serverInfo

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

...

Conserve memory during export

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

In the above code, set the Remember to set your value for <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.

...

to either the primary org (1) or a client org.

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.

Following The following is the SQL command for this:

...

...

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 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 In this sample, 1 signifies the primary/default organization.

...

...

Enable carbon copy on broadcast emails

Enables This 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.

...

Yellowfin restricts the number of rows returned from queries that involve filter values. This is the same limit that is applied for all database queries (i.e. even those without any filters) and is configurable by the user in the View builder and at the Report level. However, there is a hidden configuration option that allows users to remove this limit from filtered queries, thereby allowing Yellowfin to return all matching rows. To apply this, add the following SQL into your Configuration database:

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

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

...

Scheduled tasks that track historic executions maintain the records for the last past 30 days. To change this time limit, use the following configuration.

INSERT INTO Configuration VALUES (1, "SYSTEM", "HISTORICSCHEDULERECORDSLIMITDAYS", "60");

WhereIn this sample, 1 is the organization ID, and 60 is the number of tracking days.

...

Disable calculated field validation

Calculated fields are validated before they are saved into the database , in order to determine the data type of their resulting field. However, it is possible to disable this validation for all calculated fields (including those created via Freehand SQL).

...

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(<IP_org>1, 'SYSTEM', 'VALIDATECALCONSAVE', ‘FALSE’);

Where In this sample, ConfigData = TRUE enables validation, and ConfigData = FALSE disables it.