When opening a support ticket, it's required that a large form be completed. Among these is the Sisense Account Type, Environment, and Version. We too frequently open a support ticket only to be provided with a response unrelated to the information provided in these fields (e.g. a Linux based recommendation after specifying the issue is occurring in a Windows environment and being asked for a version number after the information was already provided). Given the global distribution of Sisense support resources, it can already take a day before expecting a response, but for that response to then be unaware of the information provided in the ticket details causes delays, extra rounds of communication (especially when our support rep doesn't realize that the Sisense response is for the wrong version), and frustrates our support teams and the clients they in turn support. And we imagine the Sisense support reps don't love finding they sent irrelevant advice and don't like seeing our support reps' confusion when they aren't already aware of the information provided in the case opening form. We appreciate Sisense support reps and want to see them support us with as little friction as possible. Thanks. ... View more

The v1 Excel exporter included functionality that would export Pivot Table widgets to an XLSX file that was aggregated just like what users see inside of Sisense in their browser. We are now using the v2 Excel exporter and it no longer has this functionality, apparently by design. I think the v2 Excel exporter should also have aggregation functionality so that the XLSX export for Pivot Tables is just like what users were seeing with the v1 exporter. We have thousands of users who have been using the v1 Exporter and are expecting this behavior. ... 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

We would like the ability to modify attribute names and shared formula names without breaking dashboards or requiring partner plugins.   ... View more

We embed Sisense into our application and produce pre-built dashboards for customers (which they cannot edit). We allow our users to create their own dashboards as well and with this comes the ability to create their own formulas. We have found that allowing them to edit the name of their formula also allows the editing of our pre-built shared formulas and our attributes. While this only impacts the user locally, it can become a support nightmare, as customers can rename our pre-built items and make it hard to them troubleshoot. We would like the ability to make these edit options more granular so that we can control (1) Shared Formula name edits (2) Attribute name edits and (3) non-shared Formula, local user dashboard, name edits. ... View more

Folders and Dashboards are only permitted to have 1 owner, this has been the case with Sisense since we first started using it 6 years ago.  The time has really come to allow multiple owners of Dashboards and Folders.  We have around 70 Designers who use our Sisense instance and being able to swap work, work jointly, used shared structures etc. adds a huge amount of time, inconvenience and frustration.  The request here is to allow multiple owners of Folders and Dashboards so that Designers can collaborate more effectively, the flexibility of such work would greatly reduce the time to deployment. ... View more

When viewing a dashboard and the filter panel is collapsed, it is near impossible for a new user to find the filter panel expand button. WHY IS IT SO SMALL??  Please update the UI so the filter panel is more intuitive to find and expand. A key feature like this shouldn't require digging through documentation on Sisense's website to figure out how to locate it. ... 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

Currently there’s no way on the Sisense UI to have an overview of when the next ElastiCube Builds are set for. Having such info available would make it possible to easily select relevant time slots to run load testing scripts for instance, but also more broadly to help understand and finetune the current Builds orchestration. In order to do so, we would like for admin roles to have access to a single table-like page that would list all the Builds scheduled in the next 24 hours with the following columns: ElastiCube name Build start date Build theoretical end date* Last successful Build duration * Build theoretical end date = Build start date + Last successful Build duration * (or NULL in the rare event where the Build has never succeeded before) Additional features: CSV Export Sort option on column headers Pagination Note: a single Elasticube can have more than one entry (in the example below, we assume the admin user opens the page at 3:00 PM and the ElastiCube_B's Build is launched every 2 hours). ... View more

Currently, when adding a date field as a value in a pivot table, the only option is the # of years/# of days/etc. We need the option to add a minimum and/or maximum date for the selected rows. The current 'work around' for this is to create an integer date, and then use a script to format the integer to present as a date. However, when exporting the data, the date shows as the integer value in the exported data, which is an unacceptable result. Adding the date as a row value solves the export issue, but displays all date values for the lowest level of detail in the data source, which is also an unacceptable result. If it was possible to add the minimum or maximum of a date field as a value in the pivot tables, this would solve all of the issues we currently have. ... View more

When viewing a Dashboard, it is impossible to determine whether there are filters being applied at the widget level without opening each widget individually and reviewing whether (a) the inheriting of Dashboard-level filters has been disabled and/or (b) if additional and/or conflicting filters have been applied at the widget-level. This makes troubleshooting and/or viewing Dashboards very cumbersome. I'd like to see a simple visual flag from the Dashboard view indicating that "there is a filter applied within this widget". It doesn't need to display what that filter is -- only that there is (or is not) a filter within the widget. ... View more