Managing pulse alerts is a nightmare, and is in dire need of improvement: 1 It's impossible to identify who added you to an alert, and there's no way to unsubscribe, so you can't manage them from the recipient side. 2. Tenant or system admins can't see all pulse alerts configured, so they have no way to identify troublesome alerts. 3. The current supported APIs don't allow identification of other's alerts. The alerts API only returns the user's alerts, and the "recent" alerts API doesn't return the ID of the alerts so you can't just delete the troublesome ones.  There needs to be some attention spent on alerts, as they are currently a nuisance and not useful.   ... View more

We have found that if an ACL in a WAT does not match the Elasticube table/column security field, it defaults to providing 'all data'. To avoid a potential human error where a table/column has been renamed, we would like the default position to be 'nothing'.  ... View more

It would be great if Sisense would allow to sort a table/pivot by multiple values, combining ASC and/or DESC and indicating the sequence for sorting, e.g. by Field 1 ASC, then Field 2 DESC, etc. For instance, I am attaching an example with two values, so that I could sort based on % Compliance first and then by # Assignments, both in descending order. Additionally, it would be great to sort a table/pivot based on a field/value not displayed in the table/pivot. Currently, we need to use a script to hide that particular column. ... View more

It's great that in the formula editor one can add as much empty space as one likes to make the code as readable as possible... spaces, returns, blank lines, etc. Also great that fields in the formula editor can be renamed from what they are in the data browser to detail, for example, how a field is filtered. We can also hack that feature to add in a [Value]*0 as a comment. Still, revisiting big formulas is time consuming because of the lack of code comments. One can create an external repository that includes comments, but formulas cannot be copied and pasted from an external repository into the formula editor, making an external solution not much more helpful. So having a way of commenting in the formula editor, or a way to store formula code somewhere else that allows for commenting that also allows for easy update in Sisense when the code changes in the external repo.   ... View more

While using the calendar date range in a filter, you should be able to type in the to and from date.  The old style filters allowed that option.  We recently switched to the "new" style (I say "new" because they are only new to us ... I think they have been available in the product for a long time).  In the new style you have to use your mouse to pick the date on a calendar, you can't type it in.   ... View more

It would be interesting to be able to modify livenessProbe and readinessProbe values in Sisense Provisioner's Helm charts (chart.png).   Currently, the values are hardcoded in the deployment charts. It is therefore not possible for us to change the values using a value file (configuration.png). ... View more

We create filters on certain records that have long names, sometimes with similar names.  The current width of the filter panel cuts off these record names and makes it difficult to find the correct record(s) to select. We suggest either making the filter panel size-able, or possibly at least wrapping the name. ... View more

Currently Embed SDK doesn't provide a function to perform the same function as clicking Restore my default filters button in dashboard filter. It would be great to add it in the future. ... View more

At the moment, the usage analytics functionality is only available for the system tenant. You can monitor activity across all tenants from there. However, this means that you cannot share usage analytics data with designers within the self-contained tenant. ... View more

In report manager, when trying to add recipients for email, we receive sisense user email id suggestions based on keyword entered. This can be confusing to users, as our end users send emails to external recipients(non sisense) and that email id suggestion is sisense internal user email. It will be really helpful if we can have a functionality to disable these email id suggestions from popping up in report manager, and avoid confusion to users.   ... View more

In dashboard filters we currently cannot add custom tool tip to filters. While using the dashboard, it will be helpful to add some tool tip description to the filter which may pop up by hovering around it or through some information icon. For example, if a user needs to use a custom filter, the JAQL syntax may not be intuitive. Using some tool tip, will help a user understand how to use the filter in a JAQL format. ... View more

Today, we can use plugins, dashboard and widget scripts to customize dashboard and widgets for scheduled emails as well as desktop. Same should be available for Pulse scripts which allow to modification of alert JAQL on the desktop, but the same script is not executed when sending alerts/notifications. This causes discrepancy between what the user sees on the desktop and what they receive in email. ... View more

Please add support of the First day of the week for the Live models. ... View more

Currently, any report having a table widget is missing IDs in<td> and <tr> elements of the <table>. We are writing automation testing scripts for which we need to have unique ids for each cell. This is seen in Campaign tables but not for Reports 2.0 dashboards. Cell id, where each cell would have some unique identifier for entire table. ... View more

We want to be able to disable jump to dashboard for certain rows in a pivot table and bars/pie-slices in various charts.  Currently we are only able to disable it completely. We would like to be able to be more specific on the disabling and only remove the jump to dashboard capabilities on the specific rows or bars.  ... View more

When the sisense user is deleted the email of this user is still in the recipients list for a report in the Report Manager. If the report Manager is configured to send the reports to external customers, the user who is no longer with the company will be receiving the reports with dashboard data as the reports for the external users are generated using the owner or an additional user. Thanks. ... View more

Idea: Allow developers to build/test add-ons in a local environment rather than requiring a live environment. Note that this would be for the purpose of creating custom add-ons for additional functionality that would require testing on the "out of the box" Sisense UI. Background/Context: In most development workflows it is common practice to work on your code locally on your machine and deploy to a local server aka "localhost" to test/view your work in the browser. An example of this is building and deploying a local React.js app to your browser. As you make changes to the code it will recompile locally and update what you see on your localhost. If you're using Sisense out of the box however, to test/view any changes to an add-on developers are forced to upload the files in some way to a live Sisense Environment. This not only limits the innovation of add-ons to developers with an active license and live environment, it makes it painfully inefficient to develop customizations on top of the Sisense application. I understand there are likely some business concerns with allowing the use of the product locally but I'd argue that there are ways to prevent that, such as enforcing some default sample data etc., but in such a way that would give developers a "local playground" to develop/innovate on. ... View more

When we are building pivot tables, sometimes there is a need to sort things by the columns. If I want to show a pivot table with a Team Lead as the rows, Total Spend and Total Volume as the values, and Weeks as the the columns, I have no way to sort this to show the date in descending order and keep the table structure the way I want to see it. I think it would be helpful to have this option. ... View more

Currently, dynamicElastiCube supports multi-model dashboards by indicating in the config at a widget level which data source to point to. However, there is no setting to do the same for dashboard filters. Thus, all dashboard filters will point to the "primary" elasticube when routing. This breaks any filter associated with models other than the primary one. ... View more