Last tested: Jan 19, 2021
Use the ordering of refinements, as mentioned in this article
Logical example:
Model file includes view file for view: a
and has
explore: b
join: a
view: +a
dimension: newfield
explore c
join: a
Only explore c should include the newfield dimension.
This content is subject to limited support.
This feature doesn’t seem to work for overridden fields (sql_table_name in my case).
Do you know of any work around this ?
Example:
view a: { sql_table_name: table_1;;}
explore c: { join a;}
view +a : { sql_table_name: table_2;;}
explore d: { join a;}
=> In both explore c and d, the view a will have table_2 as SQL source.