Currently Embed SDK doesn't provide a function to perform the same function as clicking Restore my default filters button in dashboard filter. It would be great to add it in the future. ... View more

When duplicating an Elasticube with data security rules, the security rules are not duplicated. If I want to create a new version of an Elasticube, distinct from the original, normally I will want to keep the rules, but this does not happen. Being given a choice would be ideal, but if there had to be default behaviour, it makes more sense to just keep the rules, as they can easily be deleted if they are not needed, but re-creating them, even via REST API can be fiddly. ... View more

We have a large number of dashboards and at the moment, find the navigation process for our stakeholders is not ideal as they can only "find" a dashboard if they know what words are used in the title. For example, if a stakeholder searches for complaints but the dashboard title they need is called feedback ... It won't come up as a suggestion.  A solution like having the ability to tag dashboards would massively help Thank you ... View more

I think table and custom table usage should be added to the scope of usage analytics. I have large data sources that have been around for many years. Often dashboards are unused (which I can currently track with usage analytics) and can be deleted or archived. But the data that drives them is much harder to keep track of. I have no way of knowing which tables are used in dashboards and which ones could be removed. This is especially true for custom tables that eat up build time and might not be used at all. ... View more

At the moment, the usage analytics functionality is only available for the system tenant. You can monitor activity across all tenants from there. However, this means that you cannot share usage analytics data with designers within the self-contained tenant. ... View more

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

We want to be able to disable jump to dashboard for certain rows in a pivot table and bars/pie-slices in various charts.  Currently we are only able to disable it completely. We would like to be able to be more specific on the disabling and only remove the jump to dashboard capabilities on the specific rows or bars.  ... View more

It appears that once you've created a cube or live data set, you can't rename it. You can duplicate it, but I'd really like to rename some of our models without any of the associated dashboards breaking. ... View more

There needs to be a way to deactivate user accounts rather than completing removing. We have users that will no longer have access to the system, but could come back later (for example, trail users). The workarounds are currently: reassigning security groups (means those users are still taking up licenses) writing our own user admin functionality (only makes sense if we are integrating users to another platform) Adding a 'Status' or 'Disabled' flag to the user account would accomplish this. ... View more

When I sort cubes in descending order and then click into a cube and come back to the list view I lose sorting. This can be annoying/frustrating. Can you make it so that my sorting remains until I change it? ... View more

Please add support of the First day of the week for the Live models. ... View more

Hello, I would like to porpose the following regarding formulas : - beeing able to defined formulas in the line or column section (for widget "pivot table"). Functions like SUBSTRING, LEFT, RIGHT, or CONCAT in order to reformat the content of a dimension also beeing able to use CASE function (to build buckets). - beeing able to use string function to define conditions to apply to a dimension. ie : CASE [Type] WHEN "A" THEN price * 09 WHEN "B" THEN price * 08 ELSE price END Thank you ... View more

When creating a widget with several fields, it has been time consuming and a frustrating experience to click on the "Add a field" button repeatedly to build out the widget. If there was a way to select fields and then add, it would make the experience much more efficient. 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

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

Custom Code is currently disabled in a multi-tenant environment, which is an odd thing to disable as it is among the many features that make Sisense so great because of the ability to manipulate the data within Sisense and part of the Tranform stage of ETL processes.  I am a Tenant Admin in my multi-tenant environment and I can click on Custom Code but I am not able to access the jupyter notebook environment. This creates a lot of confusion for clients who have multi-tenant environments and also takes a feature that the other clients have in single-tenant environments.  Sisense should seriously consider making this a permanent feature in all environments because it is so useful.  ... View more

Bug Click Edit on a dashboard filter that is near the bottom of the screen. The edit filter dialog pops up, but the OK button is off the bottom so you can't click it. Scrolling doesn't help. The only way to fix is it to reposition the filter so there are other filters beneath it (but then those get that problem). Applies to Sisense Windows 20.24.3.10115. In Sisense Linux, the edit filter dialog positions itself in a way shows the OK/Apply button even if you clicked on a filter at the bottom of the screen. ... View more

Idea: Allow developers to build/test add-ons in a local environment rather than requiring a live environment. Note that this would be for the purpose of creating custom add-ons for additional functionality that would require testing on the "out of the box" Sisense UI. Background/Context: In most development workflows it is common practice to work on your code locally on your machine and deploy to a local server aka "localhost" to test/view your work in the browser. An example of this is building and deploying a local React.js app to your browser. As you make changes to the code it will recompile locally and update what you see on your localhost. If you're using Sisense out of the box however, to test/view any changes to an add-on developers are forced to upload the files in some way to a live Sisense Environment. This not only limits the innovation of add-ons to developers with an active license and live environment, it makes it painfully inefficient to develop customizations on top of the Sisense application. I understand there are likely some business concerns with allowing the use of the product locally but I'd argue that there are ways to prevent that, such as enforcing some default sample data etc., but in such a way that would give developers a "local playground" to develop/innovate on. ... 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