We want to rotate the API key for our system user but need to make sure there's no downtime.  This means we need to have 2 keys working in parallel for the same user for a period of time until we can cycle all of our services to pick up the latest api key. The problem is as soon as the API key is rotated, the old key immediately stopped working.   Majority of systems out there support key rotation (like allowing a time delay before the old key expires like FB app, or ability to temporary create a second key and then we can promote it as primary once we are ready).   Key rotation is a best practice for security principles. ... 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

When filtering on a numeric field and using a Value type filter, I often want to filter on a dynamic value. As the Ranking type filter can take a formula, I would make good use of a Value type filter that also allowed for a formula. ... View more

---Summary:--- When you drill, create a filter. Link new filter and the drill-breadcrumbs, so if you change one, it changes the other. Make it an optional, per-widget setting. ---Details:--- Sometimes I build a dashboard with a "main" widget for the user to explore, plus a few indicator widgets above it. It'd be nice if, when the user drills on the main widget, their choices were applied to the dashboard filters. That way, my indicators would reflect what they've drilled into. But that should be an option in the widget settings; other times I have a dashboard with several major widgets and drilling into one should not filter the others. When the user un-drills (clicks the cross or a breadcrumb to return to the overview), that should automatically remove the associated dashboard filter. And if the user alters or removes the dashboard filter, that should carry over to the drill-down breadcrumbs. ... View more

When utilising the Fiscal Year functionality, it is frustrating that there is no option to display the calendar year as a formatting option. We are based in Australia and our Fiscal Year starts in July, so our 2023/2024 Fiscal Year (called 2024) runs from July 2023 to June 2024. If I create a simple pivot with our Date, Year (Calendar Year formula) and Fiscal Year (formula in format YYYY/YYYY), then you can see that the date is actually distorted.  There is no way to display that this date actually falls in 2023, which is the case for the first two records in the below pivot. Applying a filter with a date range handles this correctly, but it is confusing for our Finance department as to what date this is referring to. I've connected with Sisense support and they've provided a solution for a Date Display Field (thanks @AssafHanina) which does solve the issue, but then we need to have complicated rules for dashboard designers to use X field on their Dashboards but Y fields on filters, etc. I feel like an additional date format of "cy" for Calendar Year would solve this issue from the display side and make things much simpler.  Some logic already exists for "yp" for the previous year, this would be very useful for our designers to have this additional option and to keep the date as one field rather than needing a second. Has anyone else encountered this issue or would find this useful? ... View more

When a widget returns no data and is displayed in column format - it would be nice to have an option to show the column headers only to give users a reference point as to what data will be shown. Thanks ... 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

It would be really useful to have a hierarchy filter displaying parent-child relationship. Currently when we create a filter, it just displays all the members in the entity.  If there is a relationship between the members its not possible to identify it directly in 1 filter, the only way around is create dependent filters. But that too would get tedious, as everytime we have go through multiple filters to see the members in each sub filter. Example: If there is a relationship as below: In this case, the table has the name and parent name as 2 separate columns. So the filter could display members as below in a tree format which can be collapsed or expanded, such that there is a check box next to the member and user can select the individual members, or a group of members. It would give the user a clear view of the relationship between different members:       ... View more

Hello, In a multitenancy environment, it would be useful to be able to define different "look and feel" theme for each tenant. Currently, the one define on the system tenant is applied to every tenant. Thank you. ... View more

Current behavior of the Simply Ask feature doesn't support automatic saving of the modified NLQ model to the "*.dash" file. So you loose your development work after exporting the dashboard with already enabled and tuned "Simply Ask" to a "*.dash" file. After importing this dashboard back to Sisense the feature is automatically disabled. Also if a developer will enable it manually it starts running based on the "By Default" NLQ model. This forces to redo all the work on the model back again which is time consuming and not efficient. We expect Sisense to consider in the future the development work on making this more convenient for a BI engineer. If a "Simply Ask" feature will be automatically enabled on an imported dashboard with a corrected model, it would be beneficial for dashboard deploy automation and will reduce unneeded additional manual work on setting up this feature again and again for different working environments for the same dashboard. ... View more

We have a custom webhook mechanism to alert us for cube build failures. We created a single alert selecting all our cubes and adding the webhook link Given build alerts are owned only by a single person.  Ownership transfer of these is helpful when people move out of the team and new person comes in, If not,the alerts created for team will need to be re-created. Also, every time we want to add a new cube to the build alert, the owner of the common build alert should be available else we cannot add alert or will be forced to create a build alert for the absence period of the owner ... View more

Many of our clients experienced a defect in the Expand Pivot on PDF add-on in which the email body of their dashboard subscriptions included the full Pivot output... instead of the full pivot output being limited to the PDF attachment. With that defect in place for a year, a number of our clients have voiced dismay since the defect was corrected hoping that the defect will come back as a feature.  I would image that if enabled as a feature, that Embedded in Email could be unchecked to avoid including large pivot output in the email body. I imagine that users could understand their data well enough to understand whether a dashboard pivot widget would result in pages of output or not, and would be able to make the decision in the share settings for whether or not to Embed in Email or just Attach PDF or both.   ... View more

We are a multi-tenant software provider and we embed and white label Sisense.  In our setup, we have 2 models.  Model 1 is used by Engineering to create our pre-built dashboards, where we share these with specific groups we've set up so that all of our customers see our pre-built "out of the box" dashboards The second model is what we expose to our Premium users so that they can create their own custom dashboards.   There are times when our customers will create a new, custom dashboard with the second model.  These users sometimes share their dashboard very broadly.  When this happens, there are certain users that wish to remove themselves from the share.  Perhaps they don't have row-level security to see anything.  Perhaps they have changed roles or simply do not use that dashboard. Note that we do not want to allow customers to remove themselves from our pre-built shared dashboards, as this could cause support confusion as to why our analytics solution is enabled but a user doesn't see "all of the dashboards".   With the above noted, we would like a configurable means to show/hide a "leave shared dashboard" dashboard option, based on the model with which a dashboard is associated.  This will ensure that users cannot remove themselves from our pre-built dashboards (we would hide on our model) yet allow them to remove themselves from custom dashboards that were shared with them (we would show on model 2 for self-authoring) When a user leaves a shared dashboard, there should also be configuration options to alert the owner of the dashboard via email.  This email should be capable of white labeling.  It should include dashboard name, who left, and when.  Should there be links to the dashboard in the email, there must be a way to disable hyperlinks in the email. ... View more

Hello There, We need to create a data model with 2 different data sources . One databricks live and another one is an excel file with some additional data . We need to create a combined model so that we can join these two tables and get the result. Currently sisense does not support it and other providers like Power BI and Zoho supports this feature. This is a common use case for our scenario  ... View more

I recently posted a query on sisense forum to increase the offset size of a pie in a piechart. I got a response how it can be done at a widget level, but there is no feature in sisense to apply this change at global level for all pie charts in every dashboard. In fact, there should be a global space where any change for any widget could be applied to all such widgets in every dashboard. ... View more

Looking for a way to change the logo based on their corresponding theme. We can create themes for the different companies but there is no option for logo in the Theme and would like to capability to extend the white labeling past just 1 logo ... View more

The idea of this is so you could show the elasticube data on the primary axis, and then potentially low latency data on a secondary axis - allowing easy comparison of live vs historical data ... View more

As a standard offering, enable color conditions to also be displayed in the Grand Totals columns/rows. The coloring should also carry through to Excel or pdf downloads, the same for the rest of the pivot table.  Current custom script solutions are at risk of breaking with future version updates, and the Grand Totals colors do not carry through to Excel and pdf downloads. ... View more

Currently the Analytics screen displays available dashboards in a "list" view or a "tile" view.  The "tile" view includes columns "Name", "Owner", "Data Sources", "Last Published", "Last Modified", "Total Viewers", "No. of Widgets".   This is a request to add a new column "Source Folder".  This would be helpful for users with a large quantity of dashboards as they could sort by the "Source Folder".  In the future, the list view functionality could be expanded to allow grouping by this column which would further consolidate the view. Thank you! ... View more