The Data Security tab's group/user assignment window currently has a max search limit of 20 results.   The "results" search limit should be configurable because we have approx. 50 groups that need to be assigned, & it is very difficult to find/assign/manage all of the groups when the search window does not return all of the appropriate results. ... View more

See here: https://community.sisense.com/t5/technical-troubleshooting/refresh-schema-error/m-p/23594#M195 Refresh Schema fails when you have tables from two different schemas. ... View more

When we send more than one Combined Excel Report while using a dashboard having different filters on it. Names of those combined Excel sheet we get from them is same as they were using same dashboard for creating a report, which is difficult to identify when downloaded simultaneously. Can we base the name of excel sheet on Report Name itself rather than dashboard name as it will be more convenient. Thanks, Animesh Gupta ... View more

When generating the WAT token, we need to pass the Sisense user ID in the 'sub' parameter. To obtain the user ID, we must repeatedly call the Sisense APIs, which can be inefficient. It would be beneficial if we could directly include the Sisense username or email in the 'sub' parameter, thereby avoiding unnecessary API calls to retrieve the Sisense user ID. Reference Document - https://docs.sisense.com/main/SisenseLinux/using-web-access-token.htm#StructuredTokensByValue ... View more

Create a pivot widget of RSUM( [Total Quantity] ) over time (rows) and break by (columns) age range. Scanning down each column, over rows, the numbers only increase. Now change it to a line widget. The break by defaults from an RSUM within columns in the pivot to an RSUM within rows in the line chart. This is the same as not having an RSUM and doing a stacked area. Our clients expect the line chart the results from changing the pivot to a line chart, to reflect the same output as the source pivot. As it stands now, they are surprised to see negative curvature in their RSUM, think something is broken, and open a support ticket. The default behavior should be to render Break by Columns instead of Rows. As an aside, I'm having trouble coming up with, and would be interested in hearing, use cases for charts with break by set to rows.  ... View more

The content/formatting/text contained in the various Sisense-generated/automated emails is currently static. I went through a long dialog with support and determined that  it's not customizable by customers. I would like it if we could modify these emails, and I'd especially like to have access to dynamic variables that we can insert in the email body (or subject). User's first name or last name were specific for my use case, but having access to a variety of variable could be helpful. ... View more

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

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 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

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

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

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