We use jump to dashboard to allow users to view a data table to give them context to the chart they are looking at. For large data sets, this can lead to millions of records. The issue comes up when users try to then export this table. It would be nice if there was a way to set a hard limit to the number of records returned in a table/table with aggregation. When users try to download too large of a table, it impacts server performance for everyone, and the only way to really limit the tables right now and still allow them to be filterable on all required fields is not efficient (rank filter on a semi-unique identifier using the max of a unique identifier). I am looking to place simple guard rails into how much data can be exported into one file, I am flexible as to where this option presents itself and how - either a count of max records or a file size works. Having an option to set the max number of records returned in this widget type also would work. I would be fine with this as an option buried in the configuration settings page or within the admin page itself. I just want the option present somewhere. ... 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

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". ... View more

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. ... View more

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 ... View more

Hi, Currently in the filters, we are unable to directly filter a comma separated list of entries. The options available are individually selecting the members, however that can get tedious if the list of entries we need to filter are large. For example, filter more than 100 entries. The other option is using the custom option in the filter. However, that too requires JAQL code which might be difficult for non technical users.  It can be useful to have the option to directly copy paste a comma separated list of entries in the filters instead of multiselecting or using the custom JAQL option.   ... View more

Currently, if we export the pivot as an excel/csv, there is no indication of the date range it was run for in the output file. It will be really helpful to have control on the exported output in excel or csv, such that we can include the date range of the result or other filters applied in the output. ... View more

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. ... View more

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. ... View more

The list of our shared formulas can grow to be quite long.  We would like the ability to search within formulas, just as you can for attributes. ... View more

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

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. ... View more

Scenario: embedded Sisense By default, when creating a new widget, Sisense puts the user into the widget "Wizard Mode", which then requires the use to click "Advanced Configuration" to view the full-feature widget editor. We don't want our users to use "Wizard Mode" and to always be placed directly into "Advanced Configuration". This should be a configurable setting at the Admin level. ... View more

We have had several users complain that the way series selection for charts is not intuitive. Currently, when you have multiple series in a line chart and click on one in the legend, it gets disabled to highlight the others. The intent is to allow focus, but it's the wrong way around - most users expect that the item clicked should be selected and the others hidden. The current behaviour is quite painful if you want to see one series when there are several (you have to click on all the others). Is there a simple way to reverse the selection behaviour, or do we need to look at other options: wrap the control and handle it ourselves (possible?) build some drop-downs/UI to allow selection of whats shown some other neat UI work-around?? ... View more

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. ... View more

We find our clients sometimes using the widget information (i) button to provide their users with context for a widget. Their users sometimes click the button in search of information even when the designers haven't added any text to the widget information button. It would be helpful for end users to have a way of knowing before clicking that the widget information does or doesn't have additional information about the widget. ... View more

This is for LiveConnect data sources using Snowflake. We cannot filter Datetime columns at the hours level. Either "last n" hours or "between 08:00-12:00" as example. I would like to see this added as a capability of filters. ... View more

---Summary:--- When you jump to dashboard, your dashboard filters are carried over to the destination. I want to also carry any Drill Into breadcrumbs. ---Example / use case--- I right-click on a FieldA row in my PivotTable and drill it down to FieldB. Then I click on a number to Jump To Dashboard. The destination filters for the FieldB row I clicked on, but it doesn't filter FieldA. That's fine when FieldB.value occurs only as a child of FieldA.value. But some of my FieldB items are repeated in several FieldA items. For example: Many cities have a "Main Street". I right-click and drill-down on New York's street names. Then I click on data for Main Street to jump. The destination dashboard will show data for every Main Street in every city, instead of just New York's. --- Can you make JTD respect such a drill-down? --- PS: I also made a request about making Drill create dashboard filters. That would partly solve this request, but not fully: Sometimes, I don't want Drill to create dashboard filters, but I will still want the Drill to be respected by JTD. ... View more

On the Analytics page, there is a menu on the left where dashboards are listed. It is possible to create folders to organize dashboards. Folders can be nested within other folders. Currently, It is not possible to drag and drop one folder into another. This would be useful to have. ... View more