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

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
classcontents

Overview

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

...

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.

To cache dashboard tabs


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:

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


Anchor
inlinebroadcast
inlinebroadcast

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. By default Yellowfin runs reports every time you switch between dashboard tabs so that the most current report data is available to you. However, you can cache dashboard reports, by using a hidden option. To do so, add the following SQL into your Configuration database table:


Code Block
INSERT INTO Configuration VALUESValues (1, "'SYSTEM"', "DASHREPORTDATACACHING"'BROADCASTSENDINLINE', "true"'TRUE');

Where

...

1 signifies the primary/default organization

...

.


Anchor
carboncopy
carboncopy

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.

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

Where 1 signifies the primary/default organization.