Like what you see? Have a play with our trial version.

Error rendering macro 'rw-search'


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


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:


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');

To 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).

Warning: This may result in emails being delivered to recipients across a long period of time.


Where 1 signifies the primary/default organization.

To 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.


Where 1 signifies the primary/default organization.

Disable row limit on filtered queries

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 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 up.


  • No labels