WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL | Product Feedback Forum

Greggory Schwartz

·5 months ago

I'm excited to share that this IDEA has been completed and part of the 2026.1 release. Thank you to all who have voted and contributed!

Morli Ben David

·10 months ago

Hi everyone! My name is Morli, and I'm the new Product Manager for our Data Services at Sisense. It's great to meet you all.

I wanted to make sure you're all aware that we've indeed taken your feedback into our plans and are turning it into action. Specifically, Outer Join controls (including Right and Full joins, not just Left) are planned for delivery in version 2026.1.

In fact, a preview version for testing purposes is already out in 2025.4. I invite you to test it out and share your feedback with us!

I also want to take this opportunity to thank you for voting and expressing your needs and how you want them addressed. We've reached out to many of you and met to perfect the way it will be implemented.

The Voice of the Customer is a priority more than ever, and we hope you'll keep voting and sharing ideas. We actively look into ideas shared and voted here and use them as a strong factor every time we sharpen our roadmap.

I invite you to read about the feature and the preview option in much more detail in our latest blog article:

Outer joins (preview) - Release notes | Sisense Community

Thanks!

Zach Williams

·1 year ago

Another vote from me

aferah

·1 year ago

Another vote for allowing LEFT JOIN !

daat

·1 year ago

This is an absolute need to have feature, what kind of BI tool does not allow to have Left Joins??

We kindly urge Sisense to take this feedback seriously, as I can see it is affecting a multitude of customers (46 likes when I posted this). What else would you need to make this feature a priority??

Looking forward to Sisense's urgent action on this!

joffrey

·1 year ago

+1 same for me. I have been struggling for a month now because I can't find a solution to my problematic without Left Join.

omeron

·1 year ago

+1 for left joins. Really needed and there's no way around it for us.

Ben Schewe

·2 years ago

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.

CPidcott

·2 years ago

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.

marcin-vistair

·2 years ago

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

DRay

·2 years ago

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

alexgv12

·2 years ago

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

ehannscott

OP2 years ago

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

·2 years ago

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

Jango

·2 years ago

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

sahmed

·3 years ago

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

tjswing

·3 years ago

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.