Add robust folder management
We have created many folders (and subfolders) to help us organize our dashboards. It is currently very cumbersome to share folder access and ownership, which must be done for every dashboard within the folders. It would be nice if there were an easy (and native) way to share access to a folder and every dashboard within it, or to change ownership of a folder.
Folder and Dashboard Ownership for Multiple Users
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.
Simply Ask modified NLQ model import-export within a *.dash file
Current behavior of the Simply Ask feature doesn't support automatic saving of the modified NLQ model to the "*.dash" file. So you loose your development work after exporting the dashboard with already enabled and tuned "Simply Ask" to a "*.dash" file. After importing this dashboard back to Sisense the feature is automatically disabled. Also if a developer will enable it manually it starts running based on the "By Default" NLQ model. This forces to redo all the work on the model back again which is time consuming and not efficient. We expect Sisense to consider in the future the development work on making this more convenient for a BI engineer. If a "Simply Ask" feature will be automatically enabled on an imported dashboard with a corrected model, it would be beneficial for dashboard deploy automation and will reduce unneeded additional manual work on setting up this feature again and again for different working environments for the same dashboard.
Enhancing dependent filtering functionality to allow for a subset-filtering
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.Ability to more granularly control editing of Shared Formulas, Attributes, and non-shared Formulas
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.Bug: JTD does not turn off
I like the new Jump To Dashboard interface. But when I untick "Enable Jump to dashboard", it continues to offer JTD. Also, it won't let me save JTD settings after unticking Enable until I change other settings. Version L2025.1. My dashboard came from an earlier version using the earlier JTD settings.
Dynamic link generation based on values in table/pivot cells in ComposeSDK
In Compose SDK, it would be a great idea to create a unique format for crafting links from the content in table/pivot cells. Upon detecting this format, the text would be automatically transformed into a link with the full URL being crafted from the contents in the cell itself, which should have a format like <hostname>:<port number>/<additional_parameter1>/<additional_parameter2> and so on. Of course, they would be fully customizable, and the trigger for the transformation should be some kind of reserved character at the beginning or end of the cell's content. The advantages of such a solution would be that since the data for these cells is taken from the database, the values there could be freely used across any range that is desirable for the designer. These links should also work when the widget is embedded, of course.
Ability to hide columns in Pivot Table widget
When using pivot table widgets, sometimes you need to use columns that the end user does not need to see, for different purposes: sorting data avoiding grouping of values passing values to filters that affect other widgets. We consulted Sisense and several links and scripts were provided. However, we noticed that if the pivot table contains both row and value columns, the value columns might not display correctly - depending on the column width. See attached screenshot. We believe the ability to hide columns in pivot tables should be a standard and basic feature and hope to get enough support so that this gets prioritized.
Dashboards should honor the scroll bar settings instead of auto-hide.
When working in a dashboard or widget the scroll bar will automatically disappear unless you are moving the mouse within the borders of the dashboard/widget. Dashboards should honor the system settings that users have already set in their browser. For example, Mac users have the option to auto-hide scroll bars or they can activate "show scroll bars" set to "Always". Sisense dashboards will override that setting and auto-hide the scroll bar.Enhance Usage Model to include segmentation of Email Subscription vs Front-End queries
When analyzing dashboard and widget query performance, I would like to be able to focus on only front-end user queries, or just on email subscriptions, or both. Unfortunately, the source data of the Usage Analytics Model does not contain information that allows us to distinguish whether a dashboard was executed via the Web UI or through a scheduled job. Therefore, we are unable to perform the requested analysis.
