This content is now out of date.

Visit Our Community

Yellowfin Optimized Views – explained

In the Yellowfin view builder you may have noticed that Optimize View(see screenshot below) is selected by default. It sounds like a good thing, but what exactly does this do, and how does it affect your views?

Forum image

If the Optimize View option option is ticked, only the required tables will be used when building a query for that view.

For example if you have a view that joins 5 different tables, but then create a report that only uses fields from one of the tables, the other four tables will not be included in the query. There is a Mandatory(see screenshot below) option on each table that can be used to override this, so that the table will always be included in queries even if no fields from that table are selected.

Forum image

As a general rule it is recommended to have a fact table that is Mandatory, linked to other dimension tables that are not mandatory.

The impact will depend on how the view is set up. If the view has a fairly simple fact + dimensions schema, omitting the dimension tables that are unused may give a small performance increase. In more complex views, omitting some tables may change the number of rows returned by the view, as any join conditions will also be omitted.

Please Note:
When using freehand calculated fields, the tables used MUST be marked as mandatory, otherwise you will need to include these fields in the view itself.

If you have any questions on this feature, or require more information please post your questions on our support forum.

Any error messages received when using this feature can be emailed to