It would be helpful to choose where on a dashboard to add a new widget rather than it only being added to the bottom of the dashboard. ... View more

Ability to sort the items of a filter by a secondary item. Currently. for days of the week, for example, they will naturally be displayed in alphabetical order. Instead of "Mon, Tue, Wed, Thu, Fri, Sat, Sun". Sisense is only capable of displaying it as "Fri, Mon, Sat, Sun, Thu, Tue, Wed". ... View more

It's great that in the formula editor one can add as much empty space as one likes to make the code as readable as possible... spaces, returns, blank lines, etc. Also great that fields in the formula editor can be renamed from what they are in the data browser to detail, for example, how a field is filtered. We can also hack that feature to add in a [Value]*0 as a comment. Still, revisiting big formulas is time consuming because of the lack of code comments. One can create an external repository that includes comments, but formulas cannot be copied and pasted from an external repository into the formula editor, making an external solution not much more helpful. So having a way of commenting in the formula editor, or a way to store formula code somewhere else that allows for commenting that also allows for easy update in Sisense when the code changes in the external repo.   ... View more

It would be great if we were able to setup Active Directory for an individual tenant while having SSO enabled for another tenant. This would help us differentiate between our external customer facing and internal BI. ... View more

For some reason when editing a Pivot for example you can get 3 options for sorting on the "rows" - DESC, ASC, and No Sort  However when using the sort in the Pivot table itself - there is only DESC and ASC order. Could you please add the "No Sort" option to the widget too? ... View more

It would be interesting to be able to modify livenessProbe and readinessProbe values in Sisense Provisioner's Helm charts (chart.png).   Currently, the values are hardcoded in the deployment charts. It is therefore not possible for us to change the values using a value file (configuration.png). ... View more

Currently, the Area Map widget only offers two map types: World and USA. This becomes problematic if your data is limited to a specific country (Indonesia, in my case), and you only want to display that country on the map. I've managed to filter for Indonesia using the following code: ...res.geoJson.features.filter(feature => feature.properties.name === 'Indonesia'), However, this approach leads to another issue: when the dashboard loads, the Indonesian area is too small, and I have to manually zoom in. I would greatly appreciate any code or method to set the widget to automatically zoom into the Indonesian region when displayed on the dashboard. ... View more

I think table and custom table usage should be added to the scope of usage analytics. I have large data sources that have been around for many years. Often dashboards are unused (which I can currently track with usage analytics) and can be deleted or archived. But the data that drives them is much harder to keep track of. I have no way of knowing which tables are used in dashboards and which ones could be removed. This is especially true for custom tables that eat up build time and might not be used at all. ... View more

At the moment, the usage analytics functionality is only available for the system tenant. You can monitor activity across all tenants from there. However, this means that you cannot share usage analytics data with designers within the self-contained tenant. ... View more

Currently Embed SDK doesn't provide a function to perform the same function as clicking Restore my default filters button in dashboard filter. It would be great to add it in the future. ... View more

Please add support of the First day of the week for the Live models. ... View more

Currently, dynamicElastiCube supports multi-model dashboards by indicating in the config at a widget level which data source to point to. However, there is no setting to do the same for dashboard filters. Thus, all dashboard filters will point to the "primary" elasticube when routing. This breaks any filter associated with models other than the primary one. ... View more

Idea: Allow developers to build/test add-ons in a local environment rather than requiring a live environment. Note that this would be for the purpose of creating custom add-ons for additional functionality that would require testing on the "out of the box" Sisense UI. Background/Context: In most development workflows it is common practice to work on your code locally on your machine and deploy to a local server aka "localhost" to test/view your work in the browser. An example of this is building and deploying a local React.js app to your browser. As you make changes to the code it will recompile locally and update what you see on your localhost. If you're using Sisense out of the box however, to test/view any changes to an add-on developers are forced to upload the files in some way to a live Sisense Environment. This not only limits the innovation of add-ons to developers with an active license and live environment, it makes it painfully inefficient to develop customizations on top of the Sisense application. I understand there are likely some business concerns with allowing the use of the product locally but I'd argue that there are ways to prevent that, such as enforcing some default sample data etc., but in such a way that would give developers a "local playground" to develop/innovate on. ... View more

We use jump to dashboard to allow users to view a data table to give them context to the chart they are looking at. For large data sets, this can lead to millions of records. The issue comes up when users try to then export this table. It would be nice if there was a way to set a hard limit to the number of records returned in a table/table with aggregation. When users try to download too large of a table, it impacts server performance for everyone, and the only way to really limit the tables right now and still allow them to be filterable on all required fields is not efficient (rank filter on a semi-unique identifier using the max of a unique identifier). I am looking to place simple guard rails into how much data can be exported into one file, I am flexible as to where this option presents itself and how - either a count of max records or a file size works. Having an option to set the max number of records returned in this widget type also would work. I would be fine with this as an option buried in the configuration settings page or within the admin page itself. I just want the option present somewhere. ... View more

It would be great to have settings that allow adjusting the limit of values in a Pivot Table, similar to the existing option for changing the maximum number of columns displayed. Currently, we can only adjust the maximum number of columns displayed in the Pivot Table configuration. This can be done via the Admin tab by navigating to Server & Hardware > System Management > Configuration. From there, go to Pivot Table and set the Maximum number of columns to display We also have a WA for this using a widget script: https://community.sisense.com/t5/product-feedback-forum/idb-p/ideas/tab/most-recent However, it would be great to have it for all the widgets without using scripts ... View more

Hi, Working on a dashboard containing 3 pivot tables. Each have a lot of columns. (see print screen attached). In order to have a proper PDF, I need to turn the page format to A0 / landscape When exporting to PDF at the Dashboard level (from the pdf button top right), I access to a PDF setup, where I can choose the layout (landscape) and the paper format (A0), so that all the columns appears properly. In this screen, there is a Save button so that the PDF setup is saved for next time (see print screen) When exporting to pdf at a widget level, the same setup otions are available (landscape and A0), BUT THERE IS NO SAVE BUTTON. I have to redo this setup each time (see print screen). Could we have the the Save button on the widget / PDF option page, same as we have ar the dashboard / pdf option page please ? Thank you ... View more

Our users often unnecessarily/mistakenly create filters at the Widget level when, really, it may make better sense for that filter to be applied at the Dashboard level. Had a suggestion from a user yesterday to add a menu button for Widget filters that will move/convert the filter from the Widget layer to the Dashboard layer. It would simplify the dashboarding process and make it quicker, less complicated, and less error-prone for end users. ... View more

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

The helm chart supplied with Sisense allows global annotation of all service accounts within the sisense namespace. For example I can annotate an AWS role that is able to be assumed by pods: helm upgrade sisense ${sisense_chart} --namespace sisense \ --reuse-values \ --set global.serviceAccountAnnotations."eks\.amazonaws\.com/role-arn"=${pod_role_arn} While this covers most of the pods by updating all the sisense-* service accounts in kubernetes the ec-build pod (the one that actually builds the elasticube) only uses the default service account in the sisense namespace. A workaround is to annotate the default service account: kubectl annotate serviceaccount default eks.amazonaws.com/role-arn=${pod_role_arn} --namespace sisense But it seems odd that the pod would a) assume the default service account when all other pods have service accounts explicitly defined for them and b) despite having gone to the trouble of wiring up global service account annotations in helm for them not to be applied at the final step of elasticube building. This specific use case is for supplying web identity tokens to a JDBC driver so that you can interact with AWS by using a specific OIDC assumed pod role, rather than using an EC2 role or worse, static credentials in a file or connection string. Even more specifically using CData JDBC parquet driver with S3.   ... View more