WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL

[ehannscott]

WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL

[tjswing]

I've found that, for us, the need for a left join is primarily for tables. For calculations and such, it doesn't matter as much. But when we want to display a table of data, it would be a much better experience to have the left join.

However, when needed, I have gotten around it in modeling.

[sahmed]

Can you share your solution, what was your work around? @tjswing 

[Jango]

Hello @ehannscott ,

Thank you for sharing your idea in the Sisense Community. We value your input and think this is a great idea! 

This is a common ask, but due to product constraints, it will require further investment. So, in order to prioritize our development efforts, we want to gauge community interest. We kindly request you to encourage other users to vote and comment on your suggestion. The more engagement your request receives, the higher the likelihood it has of being considered for implementation.

We appreciate your efforts!

Best, 

Nir Vaknin

[alexgv12]

@ehannscott if maybe you could come up with an alternative solution to this please share it, we are presenting this need as well

[ehannscott]

My alternative solutions:

• Create dummy rows and spine tables to prevent the inner join from dropping rows. (doesn't work in all situations)
• Use Notebooks (doesn't scale for our use case)
• Live with it
• Use alternative BI software

[alexgv12]

@ehannscott thanks for sharing these alternatives will help us to see what works for us, I leave this post that is related and have other options https://community-old.sisense.com/hc/en-us/community/posts/360000477234-Left-Joining-Tables-in-Cube

[DRay]

I also found this article that may be of use: https://community.sisense.com/t5/knowledge/how-to-perform-left-join-in-the-dashboard/ta-p/8589

[marcin-vistair]

We keep stumbling upon that. This feature would be great!

[CPidcott]

Adding a voice to the chorus calling for this feature. Except it shouldn't even be a feature, how can a data analytics platform be missing such a basic function of data analytics?

The possible "solutions" floated to address this, including ones we've received directly from Sisense, are inefficient and resource intensive, and are just all around poor practice.

Please provide us with the functionality that frankly this software should never have been released without. It should not take well over a year of people asking for this for Sisense to realise they have effectively delivered a nerfed product.

[bschewe]

I'm also struggling with the limited flexibility to customize joins, particularly in tables. The workarounds described in this thread are functional but they are cumbersome, time consuming, and inefficient. The functionality of the software would be much improved if there was an option to include all values from a particular column even if there are no corresponding matches. 

For what it's worth my specific use case involves showing a count of items per a given timeframe - we need to see zeroes instead of gaps in our data.