With the recent bug fix for the "continuous timeline" option in 25.2, date range reporting is now workable for many widgets. However, there are a number of limitations that should work based on the existing features and UI. I have a couple of suggestions that are based on feedback from many Sisense users:
1. Applying a date range filter to a widget with the “continuous timeline” and “display missing values as zeros” options enabled truncates data that should still be within the range of the widget filter. For example, if I want to see costs over time from 2025 to 2035 (date filter), dates that do not have values are missing from the chart. If I remove the filter those same dates will appear with "$0" set as the value. Presumably this should not be the case if “display missing values as zeros” is enabled. Note: in this example case the widget contains fields that are from the same table, including the date field.
2. It is not possible to select “continuous timeline” and “display missing values as zeros” in pivot tables. But many users want to see the same data there as they can in other widgets. I.e. they want a date range with data for every data in that range, even if it is 0 or null. Suggestion #1 ties directly into this one, as users would want to set a custom date range filter that shows data across that range.
2 Comments
This functionality would put a lot of power at our user's fingertips. I see this as an alternative way to overcome the lack of a 'left join' option, both on the model side and for dashboard designers. That problem has already been very well documented:
WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL | Sisense Community
I believe many other users would benefit from this improvement. This seems like an attractive alternative to many of the semi-effective workarounds and plugins currently available.
- Status changed:New IdeatoNeeds Votes & Comments
Hello tbullara,
Thank you for submitting your idea!
I have brought this Idea to the product team and will post updates here as they are available.
One of the ways we prioritize development efforts is by community interest. I encourage other users to vote and comment on this suggestion. The more engagement an idea receives the higher the likelihood of it being considered for implementation.
Thank you for being a valuable part of our community!
