Filter dim by aggregate
Summary: New type of filter: Show members of dimX where MyFormula > Y. Similar to a Top filter. Details/Example: I have dimRegion and factSales. I want to report only those regions that have more than 10 sales. I can use a "top" filter to show "top 10 regions by Count(factSales)" I could add a calculated column to dimRegion showing CountOfSales and filter on that. In some cases, neither of the solutions above are appropriate. I want to create a dashboard filter on dimRegion.RegionName that shows only those regions where my measure formula is >10. One use case is that my users might build a complicated aggregate formula, like "(Sum(Revenue)-Sum(Expense))/Sum(Revenue)". They could rebuild that formula as a calculated column, but it means translating it from a Sisense formula into SQL, and it means the formula needs to be updated in two places if it changes. The user might even store the formula as a Saved Formula and re-use it across widgets; I don't want to have to understand the formula, re-implement it in SQL, and verify that my new one is correct, I just want to apply a filter "on the thing my widgets are showing". Another use case is that the dimension might be a non-unique field in a larger table. E.g. If I filter on dimCountry.RegionName. I could add a calculated column "dimCountry.CountOfRegionSales", but it's confusing and risks getting used in a way that leads to double-counting. The "correct" solution would be to create dimRegion and do a field there, but this forces the user to do SQL and data model development, which they might not have the skills for. While I want to encourage best practice (dimRegion), I don't want to force it so aggressively that I'm the only one allowed to use the system.
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 environmentNext 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.
