Support Outer Joins at the Dashboard Level
Summary: JasmineC emphasizes the critical need for supporting outer joins at the dashboard level in Sisense, as their current preview status only supports them at the modeling level. This limitation is a major hindrance for customers whose clients need self-service capabilities but cannot modify data models, therefore impacting the adoption and rollout of Sisense. Inner joins at the dashboard level are inadequate and detrimental to the solution's value. timmorell noted a similarity to a previously raised issue related to data filtering capabilities.
Outer joins are in preview now but only to be supported at the modeling level, we need them supported at the dashboard level.
For customers who's clients require self service capabilities, and do not have the ability to modify data models, this is critical functionality. In this case, not having this functionality will stunt the adoption and roll out of Sisense all together until addressed.
Inner joins, at the dashboard level does not meet requirements, and is detrimental to the value of the solution overall. This is a huge blocker for rolling out Sisense to our customers.
Edward James
·2 months agoThis feature would be extremely useful. Being able to create outer joins directly at the dashboard level would provide much more flexibility when combining datasets and reduce the need for complex model changes just to support reporting requirements.
timmorell
·3 months agoThis seems similar to the item we raised previously.
https://community.sisense.com/idea/ideas/it-would-be-helpful-to-be-able-to-filter-by-comparing-2-objects-in-the-data-mode/28942