GIT Integration - Preserve Folders between environments
We use GIT Integration to promote our projects from our DEV environment to PROD. When we execute a Pull request in PROD, all the dashboards of the project are imported into the "ROOT" folder of PROD. Would it be possible to preserve the Folder structure of the dashboards as they were placed in the DEV environment
Next and Prev on number fields
I can use the Next() and Prev() functions on date fields. I'd like to use them on number fields, and maybe even strings. Some example use cases: ([Sum of Cost], Next([Product Code])) should return the (alphabetically) next product code. I have a [Fiscal Year] field. I want to filter on that, and then have a formula show me next year's value. (And before you say "just use the standard datetime functions on a datetime field", I have different clients with different fiscal years, including one whose fiscal year start date changes year to year.) I want to do a cumulative total.
Option to have filter panel on left side in Embed SDK
Hi, We are getting a lot of requests from our user to have the option of having filter panel on left side instead of right side in embedded dashboard. We are using embed SDK to embed dashboard. Can you please include this feature in your future releases?
A bar or column chart without a category having multiple values still group values over a category
Have a Bar or Column chart with multiple values, and without a field on Categories. Note the position of the bars as though there were a field on Categories while still listing the Value title on the axis. For example, in the Sample ECommerse widget, the United States value bar is above the axis label, the United Kingdom bar is centered with its axis label, and the Australia bar is positioned below its axis label. The bars are also positioned and narrowed to leave space for all values over each value. But never will more than one value render over any given axis label. Add Age Range or something on Categories and note the grouping of the values as expected. What I would expect in the first scenario without a field on Categories is what I experience in Sisense on Windows. Each value is aligned with its axis label. The bars are also thicker because they are not reserving space for two other bars over each label.Create New Sample Data Sets with more data and more concurrent date ranges
Create a new sample data sets that have a lot more data, date ranges that are current to our dates today, has more scenarios that we see in all customers cases. Like more complex formula creations, displaying a wide range of different KPI's, have a more complex data model to show how dimensions and fact tables can work. Having a sample data set with custom code, custom tables, and custom column. Having one of the tables connect to a DW to show how the connection works as well.Improved Date Range Reporting
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.
