Currently, builds can only be scheduled in the UTC timezone. This is confusing for someone not in UTC and when you have to coordinate with external processes. The user should have the ability to schedule builds on their own timezone.  ... View more

WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL ... View more

When a user makes an edit to a report, they can click Publish Changes so that report with those edits are live for users to see. Our customers would like to have an undo button so that the edits made in the last push is reverted and the version prior to publishing changes is now the current version. ... View more

Sisense does not currently offer the ability to easily freeze the top row of a pivot table, similar to what most spreadsheet applications offer. Prior community questions on this topic (such as https://community.sisense.com/t5/build-analytics/freezing-the-header-row-for-a-pivot-table/td-p/3022) advise a workaround by manually disabling the Auto Height feature for the pivot table widget, then reducing the height of the pivot table until a widget-level scroll bar appears.  This solution only works for a very specific use case, and losing the ability for the widget to dynamically resize when populated with different sizes of datasets and/or when applying dashboard-level filters makes it less tenable. For example, if a widget is manually resized so that the header is visible when scrolling for 50+ rows of data, the widget will stay the same height if a filter is applied that reduces the dataset to 15 rows. We'd like to see if there is a way to easily freeze the header row of a pivot table while preserving the ability for the widget to automatically resize based on the amount of data. Ideally this would be a checkbox or other easily accessible widget-level setting. ... View more

The only way non-Owners of Dashboards become aware of a Dashboard being republished is if (a) they happen to notice changes in the Dashboard design since the last time they viewed the Dashboard, or (b) if the Dashboard Owner (outside of Sisense) proactively notifies Viewers that they have republished the Dashboard. I would like to see a feature where there is a visual indicator to non-Owners that informs them that "This Dashboard has been republished by the Owner since the last time you viewed the Dashboard." An Even Better If would be to allow the Owner to add notes when they republish, and these notes could be visible to non-Owners the next time they open the Dashboard. ... View more

When viewing a datamodel, there's a button to view as "List" instead of "Diagram". I sometimes use that when I need to methodically check each table. When I first open the datamodel the sort is arbitrary, so I click to sort by Name to go through them alphabetically. It'd be handy if it remembered my choice from my previous session. ... 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 the Usage cube has a dimUsers table that has User Name but it is the email address.  It can be tough to know just from an email address, who the person is.  It would be nice to have the First name and Last name of the user available.  Certainly I could try to make a connector into the mongoDB and lookup the First/Last based on the user id.  But a) I don't want to modify the out of the box usage cube and b) that seems like a lot of work for something that could be added as part of the out of the box usage cube. Thanks, Chris ... View more

It takes 5-10 seconds to load the Manage Cases page in the Support Portal. It takes even longer to open a specific case. A case can only be opened in the same window as the Manage Cases page. To go to another case requires going back to the Manage Cases page first and waiting for it to load again.  Please allow cases to be open in a new tab so that the Manage Cases page doesn't have to be reloaded so frequently, and many cases can be open and loaded concurrently rather than one at a time. Thanks for considering. ... 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

Creating security rules within the Data Security menu for Elasticubes only allows you to assign users access to values to that are already in your data. If I am creating a rules for user visibility of e.g. individual 'store references' and a new store with reference '1414' is added, I can't create a rule for store 1414 unless it is already in my data. Could there be an option to manually specify the value, rather than having to select a pre-existing value? (I am aware this possible to add via the REST API, but this is a bit fiddly for frequent small edits). ... View more

We are trying to investigate how we can trigger a Sisense data model (schema) refresh from the API. This call would be made after a data pipeline schema change. We’ll need the calls to make to "Refresh Schema" how it is done in the UI. Original Community Post by @haarishussain : https://community.sisense.com/t5/help-and-how-to/sisense-api-model-refresh/td-p/21719 ... View more

Our customers want to use the same data field twice within a filter. For example, within the field primary impression we want to include "seizure" and exclude the value "pyschiatric/behavioral problem". Is this kind of functionality on the roadmap, or can we have it added? ... 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

Our users often unnecessarily/mistakenly create filters at the Widget level when, really, it may make better sense for that filter to be applied at the Dashboard level. Had a suggestion from a user yesterday to add a menu button for Widget filters that will move/convert the filter from the Widget layer to the Dashboard layer. It would simplify the dashboarding process and make it quicker, less complicated, and less error-prone for end users. ... View more

When editing a cube or live data source, I'd like to be able to more quickly add another table.  Right now, you click on the  +DATA button at the top, and get presented with all the historical connections, etc. Instead, what if you add an "Add Table" button inside the Data Sources panel?: That is, under the triple dots in red, have a new option to quickly reuse that connection and add another table. Then you'd avoid the proliferation of connections, also (the yellow connection list, in my example). ... 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 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

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