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.
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.Allow viewers to create filters
Viewers cannot add filters to a dashboard and cannot get the "use" permission on a dashboard. I want to allow them to do so. Also, on the Community website, the "Support"/chat/ai button covers the Publish button, so it's hard to post (I had to go to browser dev tools and delete element). Also, on the community website, if I don't select a tag before clicking publish, it does a quiet fail: there's an error message hidden at the bottom of the page, but I don't see it, so I don't realise why the publish failed. It should either show an error at the top of the page, or a popup, or allow me to post without tags.
Give back the ability to manually key in dates
The new filter panel eliminated the ability to manually key in dates. Can we get that back? This is a pretty big regression and I have had many users complain about it. https://community.sisense.com/discussions/help_and_how_to/new-filter-regression/28434
Hide the "Every ElastiCube update" option on Live Models.
When using a Live Model data source, Pulse Alerts UI changes to reflect this, showing an option for the alert frequency, which only appears when the data source is a Live Model. For a dashboard subscription, the UI does not change with the option for "Every ElastiCube update" being present and seeming to be selectable, though it is not. Please hide this option when the primary data source on a dashboard is a Live Model. Optionally, you could look into hiding only when all widgets on the dashboard use a Live data source and none use an EC data source.
Excluding Filter Options from a date filter
Hi, I am currently working on a dashboard that requires two date filter. the Date From and Date To filters, to display the latest and earliest dates, which is working perfectly well. However, we would like to prevent users from selecting the first two highlighted options as shown in the attached document in both of these filters. Our goal is to exclude those options from the Date From and Date To filters. Not sure how this can be accomplished. Hoping to get a direction that will help accomplish this request Thanks TracyResponsive pivot table widths
Pivot tables are currently not responsive and it doesn't take up the full width of the available screen in an embedded dashboard. For table widgets, we can set the width to "auto" which uses the whole screen space. Similar functionality can be added to pivot tables to make the dashboards look more formal and appealing.Export to Excel from the Table widget (without plugin)
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.
