Forum

This content is now out of date.

Visit Our Community

How to set up views so that tables that are not called in the front end are not triggered in the SQL

I am creating a view where a main table Initiatives (init_id, topic_cd, sector_cd) is linked to 2 children table init_topic (init_id, topic_id, topic_nm) and init_sector (init_id, sector_id, sector_nm)

Now, when I create a report that only takes init_id, topic_cd ad topic_nm, the SQL that is fired still include the table init_sector which is not there in the report.
This then creates duplicates, unless if I use the distinct or distinct count option.

Is there a way to build the view of set up yellowing so that tables that are not called in the front end are not triggered in the SQL
Hello Guest,

Can you let us know which version and build of YF you are currently using? E.g. 7.1, 2015 20150828?

I have included three links below for your review, two from our current Wiki and one from our Forum.

View Builder Overview

Optimise View

Forum - Optimized Views Explained

Please review the following information and let us know if this helps with your present issue.

Thank you,

Kyle

Thanks for trying Yellowfin

Please complete the form below to request your copy of Yellowfin today.