Dashboard filters miss values when a dimension table is linked to multiple fact tables + data security rules
Summary: Inge Vijsma is encountering an issue with Sisense where dashboard filters do not display all values from a dimension table linked to multiple fact tables due to data security rules. The proposed workaround involves duplicating a Company table and adjusting data security rules, which they find undesirable. Filipe Pedro confirms the issue and agrees that the workaround adds complexity, suggesting that a more straightforward solution should be provided by Sisense.
We are having the following issue: When a dimension table is linked to multiple fact tables within an elasticube, dashboard filters on that dimension table don't show all values - even with left joins in place.
The cause: Our data security rules are set on a central Company table, linked to the fact tables. When a dimension table links to two fact tables (A and B) with nothing in between, Sisense picks just one path to propagate the data security rule (seemingly "shortest path" logic, arbitrary between A/B). Whichever fact table gets picked, the dashboard filter only shows dimension values present in that table - the left join is ignored for data security propagation.
Sisense's proposed workaround: Adding a second, duplicated Company table to the elasticube, linked only to the affected dimension tables (not to the fact tables). Then:
On the original Company table's data security rule, adjust the scope to "Exclude this rule when all the tables in the query are from the following list" — and list the affected dimension tables.
On the new Company table, add a new data security rule set to "Apply this rule when any of the following tables is included in the query" — and list the same affected dimension tables.
This effectively gives those dimension tables their own direct data security path, bypassing the fact-table routing issue. It works, but it means maintaining a duplicated table and duplicated rule logic for every affected dimension table.
However, this workaround doesn't feel like a real solution and is not really desirable - duplicating tables and adding data security rules just to get the dashboards filters to show correct values shouldn't be necessary. We really feel no workaround should be needed and that there should be a more straightforward way to get the intended behaviour.
Would love to hear if anyone else is looking for a fix from Sisense rather than this workaround.
Filipe Pedro
·2 weeks agoI can confirm this issue and also find the workaround quite combersome, as adds complexity to the elasticube setup, which could lead to other issues.
I feel the expected behaviour of the dashboard filters being able to show all available values in the reference tables should be either default behaviour, or at least having a much more straightforward way to achieve it, as I suspect many users will be experiencing this issue.