We would like to be able to dynamically aggregate different categories of data into a fewer number of categories to make the visualization and analysis of that data cleaner and more Viewer-friendly. Example: I may have records of a color that I want to count on. I may have these possible values: "Red", "RED", "red", "Blue", "BLUE", "blue", "Orange", "ORANGE", "orange", and so on. If I COUNT on these values I may get: "Red": 10 "RED": 7 "red": 12 "Blue": 2 "BLUE": 7 "blue": 22 ...and so on.. I'm asking for aggregation feature that I, as a user, could define based on the values in these records such taht the data above could be represented as: "Red": 29 (i.e., 10 + 7 + 12) "Blue": 31 (i.e., 2 + 7 + 22) ... View more

We have had several users complain that the way series selection for charts is not intuitive. Currently, when you have multiple series in a line chart and click on one in the legend, it gets disabled to highlight the others. The intent is to allow focus, but it's the wrong way around - most users expect that the item clicked should be selected and the others hidden. The current behaviour is quite painful if you want to see one series when there are several (you have to click on all the others). Is there a simple way to reverse the selection behaviour, or do we need to look at other options: wrap the control and handle it ourselves (possible?) build some drop-downs/UI to allow selection of whats shown some other neat UI work-around?? ... View more

Currently, the "Upsert" build behavior is only available for Build to destination. It would be great if we were able to utilize this feature in our Elasticube model where we are not building to destination. We have numerous tables containing created date as well as updated date that are attached to an id field but are unable to use the updated date field since this will bring in duplicate (or more) rows per id which we can not have. Ranking duplicates and filtering out is not a sustainable with the size of our datasets. The ability to look at the id and updated field would solve this issue without the need for a complex workaround in our data source (Big Query). Thank you! ... View more

Many of our clients have found it confusing that the formula editor will sometimes render AGG( [Data Field] ) and sometimes render [Agg Data Field]. They are the same, and people eventually learn that they are the same thing. Still, we field more support tickets than I'd like in which we find formulas that contain things like AGG( [Agg Data Field] ). For example, SUM ( [Total Quantity] ). ... View more

This idea aims to help on-premises installations or live connections to better control load. The scenario: we have a big amount of users using the Report Manager plug-in, and we cannot limit the number of reports they can create or even the minimum periodicity for their schedules. Currently any user will be able to create a big number of reports, and those reports in a worst case scenario could be sent every hour. It could case a high usage of server resources. It is possible to setup the number of concurrent reports that will be processed, but depending on the number of reports it could cause bottlenecks and big deliver delays. The idea: adding some new 'admin' settings to Report Manager plug-in: - Maximum number of reports per user: defines the maximum number of reports a unique user can create. We could use 0 for unlimited (current behavior). - Maximum number of reports per user group: defines the maximum number of reports a user group can create. Same ideia as the above, but related to user groups. It could be a unique setting for any user group, or maybe a map with specific limits for each user group. - Minimum periodicity for scheduling: currently Report Manager offers the hours, days, week and months options. For instance, if this setting is set to days, then users will not be able to select hours when creating new schedules. Current existing schedules could be kept. ... View more

The list of our shared formulas can grow to be quite long.  We would like the ability to search within formulas, just as you can for attributes. ... View more

We support multiple applications of data within a model, as there is crossover between the applications; however, our customers have granularity to choose which application data with which they are allowed to see when they create new dashboards. We use column level security for attributes today so that Application A author can only see table of data pertaining to application A while Application B author can only see tables of data pertaining to application B (note that a user can have both author rights and see all both application data). We found that this does not pertain to Shared Formulas.  This now increases the "noise" that authors see, as they are seeing formulas for an application that isn't something they can readily use. ... View more

Scenario: embedded Sisense By default, when creating a new widget, Sisense puts the user into the widget "Wizard Mode", which then requires the use to click "Advanced Configuration" to view the full-feature widget editor. We don't want our users to use "Wizard Mode" and to always be placed directly into "Advanced Configuration". This should be a configurable setting at the Admin level. ... View more

Hello, Currently the number of queries running in parallel during an EC build is set at the server level. With setting "Build / Base Table Max Threads" (4 by default). The optimised number of simultaneous queries is very much dependant on the context of the EC. For instance, an EC with 4 differents date source is more likely to accept a high number of simultaneous queries (spread over the 4 data sources), than an EC with only one data source. Therefore, I would like to suggest to make this setting per cube instead of at the server level. An alternative would be to have this setting at the Data Group level. Thank you and best regards, Franck   ... View more

It seems strange to me that each time I need to add another table to my model, I have to re-enter all the connection (or pick a recent connection). If i have 10 tables in my model, they all have their own individual connection information. If a server name ever gets renamed, it'll be a crazy headache for us. There should be a place where you define the distinct list of actual database connections (one per server or database), give it a name, apply security, etc. And then when you go to add a table to a data model, at that point you pick from the previously defined available list of connections. ... View more

After using the following property in customize JTD widget script for Pivot widget, JTD is enabled for all rows.  drillToDashboardNavigateTypePivot: 1 It would be great if we have an option of enabling JTD for specific rows.  For example, we are having 4 rows and 2 value columns in the pivot but want to have JTD linked to only "row2" and have that "row2" data passing to JTD as filter (as shown in the picture). NOTE: Customize JTD widget script referenced from Official Sisense documentation: https://www.sisense.com/marketplace/jump-to-dashboard/  ... View more

We want to rotate the API key for our system user but need to make sure there's no downtime.  This means we need to have 2 keys working in parallel for the same user for a period of time until we can cycle all of our services to pick up the latest api key. The problem is as soon as the API key is rotated, the old key immediately stopped working.   Majority of systems out there support key rotation (like allowing a time delay before the old key expires like FB app, or ability to temporary create a second key and then we can promote it as primary once we are ready).   Key rotation is a best practice for security principles. ... View more

When adding a dependent filter, the only [available] lock option is a group lock. It is more useful having the ability to lock the primary filter but allow for dependent filtering. For example, if I lock an audit title, I want to retain the ability to filter specific question(s) within the audit. If both are locked as a group, I have to ensure end users know how to filter through the widget, which can be difficult if the full text of the question does not display or the user is not proficient. ... View more

Currently when scheduling builds to run in intervals, you can choose for the builds to run once every X days, OR X hours, OR X minutes. https://docs.sisense.com/main/SisenseLinux/scheduling-builds.htm. It would be beneficial to: 1. Use Hours AND minutes so we can prevent builds scheduled for every one hour from colliding with another build on hourly (even if multiple hours) interval i.e. schedule one for every 1 hour, and one for every 4 hours and on the 4th hour they collide and prevent successful full build. 2. Allow specific scheduled time and multiple intervals i.e. start @ 7AM and repeat every hour for 6 hours, or start at x hr and repeat every x minutes.   ... View more

It’d be nice to save the layout with the .smodel file. That way, I can group related tables together. Maybe also allow comments/colours/tags to show up on the UI. E.g. I could put payroll-database dimensions on one side in blue, operational-database dimensions in orange on the other, and facts in the middle. ... View more

I have a data model with lots of tables (more than 30). That makes the UI painfully slow, e.g. when editing relationships. I think the reason is that it’s calculating where to place them on the screen. I’d like to request an alternative, crude interface that doesn’t slow down for lots of tables. Or make it work for lots of tables – e.g. do the positioning calculations when first opening, but not each time I resize or click on something. ... View more

We would like the ability to export table widget data to Excel.  While CSV is supported, we have had customer complaints because they format in the CSV file and forget to save as Excel, losing the work they've done.  We prefer this is a Sisense feature over use of a plugin as plugins require additional operational overhead to maintain and upgrade. ... View more

On the Analytics page, there is a menu on the left where dashboards are listed. It is possible to create folders to organize dashboards. Folders can be nested within other folders. Currently, It is not possible to drag and drop one folder into another. This would be useful to have. ... View more

This is for LiveConnect data sources using Snowflake. We cannot filter Datetime columns at the hours level. Either "last n" hours or "between 08:00-12:00" as example. I would like to see this added as a capability of filters. ... View more