When viewing a datamodel as "List" remember sort

Tim · ‎09-26-2024

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.

bminehart · ‎04-09-2024

Is there a way to add dynamic values inside of the text boxes that can be added to Dashboards? As far as I can tell, this is strictly static text. Maybe through scripting or something that is not obvious? If not -- this would be a useful feature to be able to link values to, for example, Dashboard filter values (records from "last 90 days" or "last 30 days") according to what has been configured.

bminehart · ‎05-08-2023

This is an "add on" request to this product request. Our customers need to be able to filter on datetime columns using a combination of both the date and the time. I'd like to see this added as a capability of filtering. For example, I'd like to filter records from "0800 yesterday to 0800 today". Or "0800 on Monday to 1700 Wednesday". Or "0800 4/1/23 to 0800 4/5/23".

bminehart · ‎05-08-2023

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.

bminehart · ‎04-08-2024

The number of source of frustration and confusion amongst our users, when building Dashboards, is conflicts/inconsistencies between Dashboard and Widget filters. I have separately suggested that Sisense introduce a visual indicator of widget-level filters and it sounds like that is planned for the future, which is great. Another related feature that a user suggested was a "reset all widget filters" button which would be a single place at the Dashboard level. If the user clicks it, it forces all Widget filters to (a) be deleted (or maybe disabled?), and (b) puts the widget filter settings back in-sync with the dashboard (meaning if the user has selectively toggled off Dashboard filter inheritance at the widget level, that will revert back to the defaults). This is a really quick and easy method to put users back to square one if they have painted themselves into a corner, so to speak.

devipras · ‎01-09-2024

Hi, Whenever an user with owner access is deleted, all the dasboard created by him are getting deleted. Also, those dashboards shared with others are also deleted. This looks like a critical issue, since the dashboard will be shared among other users, they won't be able to see any dashboard if the user gets deleted. Atleast the dashboard shared with other users should be retained. Thank You, Deviprasad

bobhenry · ‎09-24-2024

The Data Security tab's group/user assignment window currently has a max search limit of 20 results. The "results" search limit should be configurable because we have approx. 50 groups that need to be assigned, & it is very difficult to find/assign/manage all of the groups when the search window does not return all of the appropriate results.

SamAlbertCSM · ‎01-04-2024

Simply put, the ability to have a button within the UI for when new users are created within a particular data group (or similar category) to replicate permissions, DS, dashboard sharing, pulse, data model shares, etc. Even simpler, the ability to have a column within User Mgmt. to show which dashboards are shared with which user.

AlanaCummins · ‎07-18-2024

It would be cool if our end users could receive a Digest Email that is sent out on a frequent basis from Sisense. This email would be most relevant if it was based on the groups a user is assigned to already. This would ensure relevant communication, as well as ensure there is control over the reports included in the digest that the user would already have access to them. We would not want the digest email to included recommended reports the user doesn't already have access to. If it was a feature the Admin could turn on/off at the group level that would be our preference. The feature would allow the Admin to select how often the digest went out (weekly, monthly, etc). The feature would allow the Admin to select what content was included: For example: Changes, Top Used/Popular in the Users Groups (i.e. Org), and then for us I think Newly Published Reports would be ideal. This would allow an organization to choose whether every time a new dashboard is released the user is notified, for us we would prefer a section in the digest that has these 3 dashboards were released to your group(s). Other BI tools do already offer this-- Attached is an example of the Power BI digest, as reference. Thanks!

pb_si · ‎07-15-2024

The behaviour of the From/To date component appears to be causing a lot of confusion new users - we have had multiple reports mis-selecting dates and/or thinking this is a problem with Sisense. The problem appears to stem from the way the focus is automatically shifted to speed up input of the 'To' date. This is not expected by new users and causes confusion. When a date is selected in the 'From' box... If no date set in the 'To' box, move focus to 'To' box and allow the user to immediately select the 'To' Date If date already set in 'To' box, do nothing. So, the first time you set the date range the first click sets the 'From' date, and you can immediately set a 'To' date with a second click. This is handy, but at the same time confusing if you don't realise what it's doing, and in practice is causing complaints.

dougnewton · ‎08-02-2023

Would like an easy way to transfer ownership of objects to someone else. Or for a super-user admin to be able to "take ownership" of a data model or dashboard. Will make it easier to deal with when someone leaves the company and they owned things in Sisense.

bminehart · ‎05-08-2023

We would like to be able to dynamically aggregate different categories of data into a fewer number of categories to make the visualization and analysis of that data cleaner and more Viewer-friendly. Example: I may have records of a color that I want to count on. I may have these possible values: "Red", "RED", "red", "Blue", "BLUE", "blue", "Orange", "ORANGE", "orange", and so on. If I COUNT on these values I may get: "Red": 10 "RED": 7 "red": 12 "Blue": 2 "BLUE": 7 "blue": 22 ...and so on.. I'm asking for aggregation feature that I, as a user, could define based on the values in these records such taht the data above could be represented as: "Red": 29 (i.e., 10 + 7 + 12) "Blue": 31 (i.e., 2 + 7 + 22)

fschleich · ‎11-30-2023

Currently, ReportManager is only availbale on the system tenant, not on additionnal tenants. Could we have it for every tenants ? Thank you, Franck

sultanahamer · ‎03-05-2024

Cube build alerts via webhook should receive which cube has triggered the alert. This is required especially when we configure a single alert for multiple cubes As of now, we are only receiving following info. {buildSuccess: false, name: Cloned sisense alerts, type: build} With this info, we do not understand which specific cube has failed.

Camantea · ‎04-28-2023

Currently, the "Upsert" build behavior is only available for Build to destination. It would be great if we were able to utilize this feature in our Elasticube model where we are not building to destination. We have numerous tables containing created date as well as updated date that are attached to an id field but are unable to use the updated date field since this will bring in duplicate (or more) rows per id which we can not have. Ranking duplicates and filtering out is not a sustainable with the size of our datasets. The ability to look at the id and updated field would solve this issue without the need for a complex workaround in our data source (Big Query). Thank you!

bminehart · ‎09-10-2024

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.

dougnewton · ‎09-10-2024

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).

rishabsurana · ‎09-09-2024

When generating the WAT token, we need to pass the Sisense user ID in the 'sub' parameter. To obtain the user ID, we must repeatedly call the Sisense APIs, which can be inefficient. It would be beneficial if we could directly include the Sisense username or email in the 'sub' parameter, thereby avoiding unnecessary API calls to retrieve the Sisense user ID. Reference Document - https://docs.sisense.com/main/SisenseLinux/using-web-access-token.htm#StructuredTokensByValue

reporting-mryum · ‎06-23-2024

We currently have SSO enabled for our product development but we also have internal users who need to reset their password once in a while for personal or security reasons. But the current behaviour is "if you have SSO enabled, users won't receive an email when they click forget password and only admins can reset their password instead". This is very troublesome and if you have a large organisations with hundreds of internal users, it is very difficult for the admins to manage that expectation. Would really like to get some help from the dev team and allow "forget password" even when SSO is enabled!

DrewGillow · ‎06-20-2024

Goal Enable dynamic alerting based on history using formulas Enable reuse of conditional coloring rules for pulse threshold Background Pulse allows you to trigger off of a threshold (e.g. > 10,000, <= 10) Conditional Coloring of widget values allows for functions (e.g. Min([Months in Date], [# of unique Transactions]) Perhaps the Automatic anomaly detection does this, but we have no visibility into what is results in an anomaly. Also not sure if you have to wait for the anomaly detection to learn. e.g. the cube has been built every day for years and has years of data, but the widget was only created a couple weeks ago and the pulse alert was added yesterday. Will it detect anomalies or out of bound conditions that we could write with a formula Desired Functionality Enable use of functions in Pulse thresholds similar to Conditional Coloring of widget values Ideally enable reference to the Conditional coloring options for the widget. The dashboard designer already built it into the dashboard. The user just wants a pulse alert when the widget turns RED. Provide means of selecting from existing conditional coloring rules (Whether they are static values or forumlas) when building/editing the Pulse tile.

Sisense Community

When viewing a datamodel as "List" remember sort

dynamic values in text widgets

Date Time Filter Combining Days and Times

Need Visual Indicator of Widget-Level Filters

button to reset all widget-level filters

On Owner deletion, all dashboards created by him should not be deleted

Data Security Search Limit Max

Clone a user

Email Digest for end users

Date picker UX is confusing for new users

Transfer ownership of objects (data models, dashboards)

Aggregate Categorical Data to Simplify Analysis

Having access to ReportManager on a multi tenant environnement

Cube build alerts via webhook should receive which cube has triggered the alert

Elasticube Build Behaviour - Upsert

One-Click to Convert Widget Filter to Dashboard Filter

Quickly add another table from an existing connection

Include the option to add the Sisense username in the 'sub' parameter when generating the WAT token.

Allow user to "receive forget password email"/"reset their own password" when SSO is enabled

Allow Functions and reuse of conditional coloring rules in Pulse Thresholds