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

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

It seems strange to me that each time I need to add another table to my model, I have to re-enter all the connection (or pick a recent connection). If i have 10 tables in my model, they all have their own individual connection information. If a server name ever gets renamed, it'll be a crazy headache for us. There should be a place where you define the distinct list of actual database connections (one per server or database), give it a name, apply security, etc. And then when you go to add a table to a data model, at that point you pick from the previously defined available list of connections. ... View more

This idea aims to help on-premises installations or live connections to better control load. The scenario: we have a big amount of users using the Report Manager plug-in, and we cannot limit the number of reports they can create or even the minimum periodicity for their schedules. Currently any user will be able to create a big number of reports, and those reports in a worst case scenario could be sent every hour. It could case a high usage of server resources. It is possible to setup the number of concurrent reports that will be processed, but depending on the number of reports it could cause bottlenecks and big deliver delays. The idea: adding some new 'admin' settings to Report Manager plug-in: - Maximum number of reports per user: defines the maximum number of reports a unique user can create. We could use 0 for unlimited (current behavior). - Maximum number of reports per user group: defines the maximum number of reports a user group can create. Same ideia as the above, but related to user groups. It could be a unique setting for any user group, or maybe a map with specific limits for each user group. - Minimum periodicity for scheduling: currently Report Manager offers the hours, days, week and months options. For instance, if this setting is set to days, then users will not be able to select hours when creating new schedules. Current existing schedules could be kept. ... View more

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

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

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

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

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

When replacing a server, or testing an upgrade, we often find our clients taking a backup of their Sisense database and restoring it to another server. After updating the server identity in the mongodb, it's pretty much ready to go. However, use dashboards all reference the old server and have to be updated. This is a manual process that the users themselves one dashboard and data source at time. An administrator cannot easily do that work on their behalf. Acknowledging that there is a replace_datasource API call that allows you to apply a new server and data source to a single dashboard, I would love an easier a way to update just the server across all dashboards. ... View more

Opening a dashboard which leads to a temporary error will redirect the user away from the dashboard URL to a 'dedicated' error page, e.g. 'https://xxxxxxx.sisense.com/app/main/error?status=404'. If this is a temporary error and the user refreshes this page they will never return to their intended destination - they are stuck on the error page forever. This causes confusion for our clients. Is there a way to change the way errors work so that I'm not redirected to a 'dedicated' error page and instead I can refresh the page and see my intended dashboard once the error is resolved? ... 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

Allow widget designers to turn off the display of the Grand Totals calculation for certain columns in a pivot table. Situations exist for which it is highly beneficial to display the Grand Total of a select few columns in a pivot table, and not to show others as they can be misleading or distract from the primary purpose of the pivot table. I envision an implementation that enables the Grand Total to be toggled on/off for each column, with the default being 'on' for all columns. ... 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

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Designers cannot save formulas for shared use. This is problematic in two scenarios: 1. End users (our customers’ customers) are Designers 2. Data models are shared across multiple tenants (with row level security) Without this the customer is forced to either manage hundreds of separate data models, which is not sustainable, or to remove all ability to save formulas, which is not acceptable for users. The “Shared Formulas” feature should allow for permissioning; something similar to “limit sharing to users’ own groups” would work. ... View more

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