Hi, Currently in the filters, we are unable to directly filter a comma separated list of entries. The options available are individually selecting the members, however that can get tedious if the list of entries we need to filter are large. For example, filter more than 100 entries. The other option is using the custom option in the filter. However, that too requires JAQL code which might be difficult for non technical users.  It can be useful to have the option to directly copy paste a comma separated list of entries in the filters instead of multiselecting or using the custom JAQL option.   ... 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

Is there a way to add dynamic values inside of the text boxes that can be added to Dashboards? As far as I can tell, this is strictly static text. Maybe through scripting or something that is not obvious? If not -- this would be a useful feature to be able to link values to, for example, Dashboard filter values (records from "last 90 days" or "last 30 days") according to what has been configured. ... View more

The number of source of frustration and confusion amongst our users, when building Dashboards, is conflicts/inconsistencies between Dashboard and Widget filters. I have separately suggested that Sisense introduce a visual indicator of widget-level filters and it sounds like that is planned for the future, which is great. Another related feature that a user suggested was a "reset all widget filters" button which would be a single place at the Dashboard level. If the user clicks it, it forces all Widget filters to (a) be deleted (or maybe disabled?), and (b) puts the widget filter settings back in-sync with the dashboard (meaning if the user has selectively toggled off Dashboard filter inheritance at the widget level, that will revert back to the defaults). This is a really quick and easy method to put users back to square one if they have painted themselves into a corner, so to speak. ... View more

Would like an easy way to transfer ownership of objects to someone else.  Or for a super-user admin to be able to "take ownership" of a data model or dashboard.  Will make it easier to deal with when someone leaves the company and they owned things in Sisense. ... 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

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

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

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

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

Currently, ReportManager is only availbale on the system tenant, not on additionnal tenants. Could we have it for every tenants ?   Thank you, Franck ... 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

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

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

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

Hello, It would be good to be able to export data to Excel from the Dashboard menu. Currently, one dashboard containing 3 widget requires to go to each widget and export to Excel, resulting in 3 diffrente Excel spreadsheets. Users are requesting to be able to export every widget data into one single Excel file / each data widget in one seperated tab. This features exists in ReportManager, so it is difficult to understand why it is not available from the dashboard view. Thank you and regards, Franck ... View more

Hi, We are facing some issues in the hour timezone related to builds. There's no way to change the UTC setting for the build schedule. It's very confusing and it's generating many issues in timezones when there are changes in the hour due to summer/winter time adjustments. We tried to change the timezone in the upgrade process, but the build schedule only works in UTC. This is a nightmare for data administrators. We need to be able to set the local timezone as the build schedule setting.  Best ... View more

Allow widget designers to turn off the display of the Grand Totals calculation for certain columns in a pivot table. Situations exist for which it is highly beneficial to display the Grand Total of a select few columns in a pivot table, and not to show others as they can be misleading or distract from the primary purpose of the pivot table. I envision an implementation that enables the Grand Total to be toggled on/off for each column, with the default being 'on' for all columns. ... View more

Every day we process our elasticubes and they always process in the same sequence.  Users are able to create dashboards that have widgets from different elasticubes.  However when they select to send the dashboard by email on "Every Elasticube Update" this sends after the first of the elasticubes has processed, rather than waiting until all of them have updated.  This means users are emailed dashboards that have some data correct, and some that is old. I think the solution would be an option to send after all of the elasticubes in the dashboard have updated, or to select a specific one, if the elasticubes generally build in a particular order. It would be good if this could be considered for enhancement as users wouldn't want to receive partially correct dashboards in this situation. Thanks, James ... View more