Currently, ReportManager is only availbale on the system tenant, not on additionnal tenants. Could we have it for every tenants ?   Thank you, Franck ... 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

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

the display format of the cube build time is shown as "Nov 8, 2023 2:00:01 AM" We should have option to format it to "11/08/2023 02:00 ' i.e. MM/dd/yyyy HH:mm:ss' ... View more

We have created many folders (and subfolders) to help us organize our dashboards. It is currently very cumbersome to share folder access and ownership, which must be done for every dashboard within the folders. It would be nice if there were an easy (and native) way to share access to a folder and every dashboard within it, or to change ownership of a folder. ... View more

Please enable the possibility of selecting a default CSI (storage class interface)  from a set of existing CSIs so that it may be used as default Sisense persistent storage option. This is is a necessary feature for persistence of storage in cases such as autonomous cluster scaling or rebalancing, as well as disaster recovery.   ... View more

Currently, dynamic/parameterized datasets are not supported in BigQuery connections. You can parameterize the service account information, which is great, but it would be helpful to be able to use a parameter to swap the dataset in the BigQuery connection based on who's currently viewing the dashboard.   For reference, parameterized datasets and schemas are supported by other database engines: Azure Synapse MS SQL MySQL PostgreSQL Redshift Snowflake ... View more

We would like the ability to export table widget data to Excel.  While CSV is supported, we have had customer complaints because they format in the CSV file and forget to save as Excel, losing the work they've done.  We prefer this is a Sisense feature over use of a plugin as plugins require additional operational overhead to maintain and upgrade. ... View more

We would like the ability to modify attribute names and shared formula names without breaking dashboards or requiring partner plugins.   ... View more

We create a basic set of pre-built dashboards that we publish, where business users can view but not modify.  We also have two-tiers of analytics offering for business users (standard and premium).  On our common, pre-built dashboards, which are available to both standard and premium, we would like the ability to expose Simply Ask to only those users of premium (hiding it from those who are standard).   While this may be achievable via a 2-model, 2-dashbaord set approach, we desire to manage a single set of dashbaords and model to simplify deployment overhead and maintenance. ... View more

We need a view that shows us which dashboards are dependent on which table in the datamodel. We want to remove some tables, but because we have many dashboards we don't know where exactly that table data is being used so it's very risky to change/delete tables. The depedency granularity of the data model is good but not enough. ... View more

We embed Sisense into our application and produce pre-built dashboards for customers (which they cannot edit). We allow our users to create their own dashboards as well and with this comes the ability to create their own formulas. We have found that allowing them to edit the name of their formula also allows the editing of our pre-built shared formulas and our attributes. While this only impacts the user locally, it can become a support nightmare, as customers can rename our pre-built items and make it hard to them troubleshoot. We would like the ability to make these edit options more granular so that we can control (1) Shared Formula name edits (2) Attribute name edits and (3) non-shared Formula, local user dashboard, name edits. ... View more

A user would like to remove the title from the secondary indicator. Unchecking the Title box works for only the primary value. They would like the same functionality for the secondary. ... View more

Hi, We are facing some issues in the hour timezone related to builds. There's no way to change the UTC setting for the build schedule. It's very confusing and it's generating many issues in timezones when there are changes in the hour due to summer/winter time adjustments. We tried to change the timezone in the upgrade process, but the build schedule only works in UTC. This is a nightmare for data administrators. We need to be able to set the local timezone as the build schedule setting.  Best ... View more

We disabled the new Simply Ask option in the Sisense configuration but it's still showing as a disabled option when you click a dashboard's context menu. We submitted this as a defect but were told that it's "by design". It's by design to show an option that's been disabled? We don't want users to request the option be turned on, as the hover text suggests. ... View more

Would you consider allowing the retrieval of files from the nodes with the file management so that end-users can retrieve logs with having ssh access. ... View more

As of L2023.3, in Sisense’s Helm Charts , “Tolerations” are supported by the micro-services. It prevents end-users from configuring “Taints” on the node that they want to dedicate to Sisense. Since no “Taints” are configured, so all nodes can become eligible to host Sisenses’s pods. They experienced that scenario when pods from some other application services were scheduled on a Sisense node. Would you please consider allowing the pods to be protected not only with  “Toleration” but also with “Taints”. The justification for this is that, even though it is mentioned in prerequisites documents that Sisense should be installed on dedicated servers, there is a non-negligible factor from the customers perspective that is the overhead administrative costs, especially for customers who must already manage numerous clusters for several applications, multiple environments, and redundancy.   ... View more

There are cases where the Sisense queries have to read from views. Would you consider allowing to issue queries like “ALTER database.materializedView REBUILD”  instead of only allowing select commands, in this case this would allow to refresh data that would be selected by the jdbc connector. ... View more

Some end-users have strict environmental and security constraints for their operations.  Please consider including M.I.T. Kerberos binaries and environment variable so that JDBC connectors could leverage Kerberos without having to access Kubernetes hosts machines. ... View more