When creating a new table in an Elasticube, the area to write code into takes up a fraction of the screen space. Please make the pop-up to write code for tables stretch across the whole screen so users can see more lines of code at once. Or make the pop-up window adjustable so we can move it to be as big as we like.  ... View more

We get requests to add full charts to a Pulse.  The option doesn't currently exist in the dropdown. ... View more

We use the SSO JWT option for Single Sign-on. In Single sign-on configuration, we specify the Remote Logout URL. We want a way to specify this remote logout URL at the user group level. ... 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

Some end-users have several environments where they must provision Sisense and they strive to standardize and automate the processes as much as possible for efficiency. It would be great to be able to extend standardization and potential automation of configuration to the Helm Chart level: Please include some ways to enable feature or disable feature with the helm chart so that if we want to enable file management everywhere we could provide a value to all our helm charts so we can have uniform configuration. ... 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

When Highcharts is installed there is no option to choose what kind of scroll bar to use for a Widget. It would be nice if the designer could choose the Highcharts zoom bar or the regular scroll bar per Widget or Dashboard ... View more

Please add the ability to control widget zoom level via the Highcharts Navigator legend with the mouse wheel on Bar Chart type widgets via an option that can be enabled optionally. This would be similar to how map zoom can be controlled via the mouse wheel. ... View more

Currently a user can only have access to one tenant at a time. In my organisation we are only able to log into Sisense with an AD account, so users can only have one login each. All of our reporting and elasticubes are currently on the one original System tenant. I need to set up a second tenant to hold some highly confidential elasticubes and then be able to grant access to this tenant to a select few users, but with them still retaining access to the original system tenant. The current setup means these users would lose access to all of their other dashboards on the original tenant. ... View more

We propose adding a valuable feature to our dashboard UI: the ability to export a comprehensive list of all data models, including both Elasticubes and live models. This enhancement is essential for efficiently monitoring model changes before and after Sisense upgrades. Presently, this process involves manual actions like taking screenshots or exporting a text file using 'si' commands, but it lacks the capability to export live models and essential metadata such as data model type, owner, last modification date, last publication date, activity, and size. By introducing export functionality in formats like CSV, users will be equipped to easily track and compare models, quickly identifying any discrepancies or replacements. This improvement will significantly streamline model management and ensure seamless transitions during upgrades. ... View more

Currently the box and whisker plot is not supported when using a live model. When the widget is created, it has an error and won't show any data. We would really like that to be supported on the live model. Article showing that its not supported: https://docs.sisense.com/win/SisenseWin/live-connect.htm ... View more

There are three features for BigQuery connections that would make your Edit Chart interface great. Show descriptions on the tables and fields: BigQuery supports adding a description to the fields and tables themselves. This information is often useful, and I find myself going to check the documentation on BigQuery consola in Google Cloud itself. We make use of this feature. Other databases also allow defining comments on tables and/or fields. It would be great to show them on the intervace via a tooltip when you put your mice over the field (right now is showing the type only) Display amount of data to be processed: one of the characteristics of BigQuery is that you pay by the amount of bytes you process. Building queries that are "efficient" is tricky task. Having a visual clue on the cost of the query allows me to understand better, before adding something in a dashboard or even running the query, how much data is going to consume. Also, if you tie that to the fact that I usually want to run the query using filters, and that there is no way for me to change filters in the editor, it makes my life miserable, because I need to copy the query, go to Google console, replace the generic filters [name=value] by real SQL filters, make a sense of the cost in SQL, etc... miserable experience. Show partitioned tables differently: For example, on Google Cloud BigQuery editor, partitioned tables are shown with a different icon than normal tables. Knowing if a table is partitioned, and knowing also which fields are the ones partitioned, would help to build efficient queries without leaving Sisense. Right now I find myself jumping in and out sisense. This takes time, and you are already showing all fields and tables in there, it would be great to just use a different icon for partitioned tables. That would be already helpful. Displaying the amount of data processed, to keep costs slim, would likely be the top thing (and Google does have API / command line in order to get the amount of bytes to be processed by a query). ... View more

I use Chrome browser. I keep multiple tabs of sisense opened. When the session expires, it expires on ALL the tabs (which makes total sense).  The problem is that all those tabs get redirected to the login page and I need to login on each and every one of them. It does not detect I've logged in in another tab, neither if I hit the browser Refresh button it will detect the login and redirect me to the page I was in before I got logged out.   This is annoying because I have to either login again, or open a new window and search for the dashboard I had open. Ideal expected behaviour (preferred, but probably harder): Once I'm logged out on several tabs, logging in one of them should make the others notice and log me in automatically. Good-enough behaviour ("easier"): Once I'm logged out on several tabs, logging in one of them should allow me to go to other opened tabs, which are showing the login windows, and refresh them (e.g using Ctrl+R) so that itwill automatically detect my session and redirect to the page I was before I was logged out.   This will save me a lot of time and make sisense less annoying. ... View more

we want larger area to edit and view widget description ... View more

Currently in version 0.9 /datasources/{title} is used for cancel all queries but also return a datasource. It is the only way to get a datasource by title. The other alternative is use the get datasources endpoint but the filtering does not work to filter by title.  It would be really good to have an endpoint to get the datasource by title. ... View more

The Sunburst chart is a great way to view multilayered data and obtain high level values and percentages from the source. Surprisingly, this visualisation does not support Jump to Dashboard (JTD) functionality which I would like to request. The ability to drill into the data is vital and provides users with an understanding of what sits beneath the chart should they require the detail.  ... View more

Hello, How about having a better control over queries parallelism ? My use case : Elasticubes using 2 connections : DB1 / DB2 Currently, the parameter BaseTableMaxThreads (sets to 2 for us) controls how many queries can run in parallel, whatever the connection. During build, we frequently see situations where we have 1 query on DB1 and another one on DB2. Reducing the level of parallelism was necessary to limit contention on one connection but it would be fine to have 2 queries on DB1 and 2 queries on DB2 at the same time. My proposal is the following : having a parameters to controls the level of parallelism per connection and not per build. Thank you.    ... View more

Hi. It would be cool to have a possibility do use external RabbitMQ instead one provided with Sisense Provisioner and hosted in Kubernetes cluster as StatefulSet. We would like to use managed rabbit cluster from AWS. The same case could be for MongoDB with AWS Document DB. ... View more