Besides the UI configurations that Yellowfin has to offer, there are certain settings that you can alter using SQL.
To enforce a global language
It is possible to use a hidden configuration to override the global language of a Yellowfin instance. 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");
Where, “zh_CN” refers to the Java language locale code for the language you wish to enforce.
And 1 denotes the primary/default organization. (Note that this is done system wide, and cannot be enabled for specific client organizations. Therefore this value must always be 1).
To 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');
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.
For view joins
During the creation of views, you can configure outer joins to be treated as inner joins when creating View relationships in the database.
Following is the SQL command for this:
INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(1, 'SYSTEM', 'DISABLEOUTERJOINCHECK', 'TRUE');