When editing a cube or live data source, I'd like to be able to more quickly add another table.  Right now, you click on the  +DATA button at the top, and get presented with all the historical connections, etc. Instead, what if you add an "Add Table" button inside the Data Sources panel?: That is, under the triple dots in red, have a new option to quickly reuse that connection and add another table. Then you'd avoid the proliferation of connections, also (the yellow connection list, in my example). ... View more

Some of our customers are being forced to upgrade Mongo, and we need to upgrade our drivers in order to match. On 2023.7 we are using driver version 1.3.11 which is not compatible with MongoDB 4.2+ and our customers mentioned they are being forced to go to MongoDB version 5 or 6. ... 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

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

I would like to be able to run a "lineage/dependency" report in Sisense. Something that will tell me for all the cube/live data sources: - Data source name - Type (cube/live) - Dates of the data model (created, modified, last built) - Data sources being referenced and type (web service, database, etc.) - Details of each data sources (SQL Server, servername, database name) - Tables or objects being referenced by those data sources It's important for managing the environment to know what we are using, or have an easy way to know what data sets/dashboards would break if a table's structure were changed in the database. ... View more

When using Starred Filters, end uses can create their own filter and save the selection for repeat use. However, any Starred Filter created will be visible to all users regardless of their Group or Parameter assignment. This is because these items are stored in the Data Browser as additional elements linked only to the data source and not to a user or group. As a result, this causes confusion, lack of control where one end users Starred Filters can be removed by another and concerns about data security. Appreciate utilising multitenancy would be a solution, however, this is not possible in all circumstances and requires a significant amount of additional administration.  I am recommending a functionality change to control / limit the visibility of Starred Filters to the User or Group that created them.  ... 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