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

Idea: usage analytics reports can tell what reports use a certain field? Filter by a certain field in the usage analytics report and you will see all dashboards using that field.  It would also be beneficial to track table usage in dashboards too.  Use Case: region will be renamed to region_usa in our sql query and this could potentially break dashboards. to be proactive, i would like to know what dashboards are currently using the field 'region' so that I can redirect them to the correct field, 'region_usa' once the sisense schema & sql has been updated. ... View more

People sometimes build bad data models. Rather than them doing more training (or asking me to help), you could build a tool that points out common problems. The user would click a button, wait a minute or so, and then get a list of potential problems and suggested changes. The tool would describe an example using their data that they can use to prove the problem (e.g. "filter a widget by Location and Date and then you see it's double counting the Dollars field"); that would be more motivating than an abstract argument. Not only can they debug themselves, doing so will be better than training for teaching them to design better data models. Here are my ideas for issues to look for. They might not always indicate a problem, but you can point them out for the user to decide. Do they use a convention for distinguishing Fact and Dim tables? Typically "fact" and "dim" prefixes for table names. Does any widget use a dim-table field in an aggregation in a Values pane formulas? Does any widget use a fact-table field in a non-values pane, or as a members filter in a formula? Do any dim-tables join to a fact-table via another fact-table? Does any pair of tables have multiple relationship paths of the shortest length? (Should be only one short path and it shouldn't include a fact table, but there might be several longer ones via other fact tables.) Any many-to-many relationships? Sometimes this is intentional and the user is meant to select a single item from a dim-table, so maybe ignore it if all uses in widgets filter one side of the relationship. ... 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

Recently, we were trying to create a widget using the RPAVG function for a rolling 30-day average, which broke our connection to the live model while working (to an extent) on an elasticube. The function worked past the first 30 days on the elasticube, while the first thirty days were (SUM N )/ N. This formula works past those thirty days, but for the first value, for example, gives simply the first value.  A new version of these functions would be greatly appreciated.  ... View more

While it is possible to Lock a filter so that users can't change it, sometimes they get confused by the presence of that filter and want to try to change it, which results in a support call to us.  There could also be times when the filter criteria itself is sensitive. We should be able to right-click on a filter and choose "Hide from Viewers". This would also have the benefit of cleaning up the user interface a bit, so viewers don't have to wade through criteria that they can't control anyway. ... 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

Instead of having to manually set the same format for each date type over and over, it would be nice if you could set defaults for each date type (Year, Quarter, Month, Week, Day) somewhere and have everything default to that with the ability to change away from the default if needed.  This could be done in the same area we set First Day of Week and Fiscal Year for the server. ... View more

1. View all history of builds and its corresponding logs from the cubes. Because, I could not see the last build failure reason, if another build got started. I need to wait for another build to complete or fail. 2. View all history of changes and provide a way to revert as in Google docs for both the cubes and dashboards. Some times, if something went wrong, we should just be able to revert to the previous version and continue from there. 3. Provide a way to view the list of cubes in the queue waiting for the build. Also, allow remove or disable them for a period or rearrange the queue to build. This will help in prioritizing something manual on demand. 4. If a cube build fails due to the memory or other configurations issue, provide suggestions like what has to be changed and based on what before triggering another build. 5. Provide a page to derive the suggested the configurations like memory, cpu, timeouts etc by collecting details like 1. Number of cubes, 2. average cube size, max cube size, min cube size, or number of cubes by size range say <5g, <10G, <20G, <40G etc.., 3. Frequency of the build per cube etc.. 6. Provide a page to view all the slow running dashboards, slow running queries and some suggestions to improve it. 7. Some times, if a dashboard got changed and republished, it is not getting applied to all the users. Provide a way to view the version of the dashboard the user may view. 8. Between builds, if there is not much change in the data, Sisense build should go faster. Provide a way like one common place to build each table from other sources individually and keep it ready. From there, if we build say functional cubes, it should build in flashing fast using the locally stored data. I see the cubes are pulling the data faster from relational db but very slow from mongodb. Now, if we are pulling data from another sisense cube or from the source no big performance difference. 9. Also, I am not sure, if we are restarting the nodes, should we necessarily mark the cubes in queue as failed, instead adding back to the queue as it was before the restart and just marking the actual cube got failed should be good enough. More later .. Thanks, Muthusamy J ... View more

Currently the values that get displayed in a "text" based dashboard filter is sorted by default in ascending order. This is ok for most cases. But for certain cases (e.g. date as text) - we wish to showcase values in descending order. Hence, the feature request for allowing sorting in dashboard filters. ... View more

It would be helpful to choose where on a dashboard to add a new widget rather than it only being added to the bottom of the dashboard. ... 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

Ability to sort the items of a filter by a secondary item. Currently. for days of the week, for example, they will naturally be displayed in alphabetical order. Instead of "Mon, Tue, Wed, Thu, Fri, Sat, Sun". Sisense is only capable of displaying it as "Fri, Mon, Sat, Sun, Thu, Tue, Wed". ... View more

It would be great if we were able to setup Active Directory for an individual tenant while having SSO enabled for another tenant. This would help us differentiate between our external customer facing and internal BI. ... View more

In browsers, usually links can be right-clicked. You get a menu including "Open in new tab" and "Copy link". Some Sisense links block this behaviour: e.g. the list of dashboards and jump-to-dashboard links. It'd be nice to get it back. To be clear: I do not want every link to open in a new tab. That would be annoying. I just want the option to do so. For example, here's a link where the right-click does work:   ... View more

As an admin, have an option at the top of a dashboard to be able to view it as another specific user.  For example, if user John Smith is set under the data security on a cube to only have access to rows for a certain region, the ability to view a dashboard as John Smith would make checking user access very easy. ... View more

It's not possible to create a dashboard filter using formulas. I could create a dashboard filter only with variables that are present in a data source. I am able to create a value in pivot table and then use it as widget filter, but it can't be done to other widgets that are not pivots. ... 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