Hello, I would like to porpose the following regarding formulas : - beeing able to defined formulas in the line or column section (for widget "pivot table"). Functions like SUBSTRING, LEFT, RIGHT, or CONCAT in order to reformat the content of a dimension also beeing able to use CASE function (to build buckets). - beeing able to use string function to define conditions to apply to a dimension. ie : CASE [Type] WHEN "A" THEN price * 09 WHEN "B" THEN price * 08 ELSE price END Thank you ... 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

When creating a widget with several fields, it has been time consuming and a frustrating experience to click on the "Add a field" button repeatedly to build out the widget. If there was a way to select fields and then add, it would make the experience much more efficient. Thanks! ... View more

The only way non-Owners of Dashboards become aware of a Dashboard being republished is if (a) they happen to notice changes in the Dashboard design since the last time they viewed the Dashboard, or (b) if the Dashboard Owner (outside of Sisense) proactively notifies Viewers that they have republished the Dashboard. I would like to see a feature where there is a visual indicator to non-Owners that informs them that "This Dashboard has been republished by the Owner since the last time you viewed the Dashboard." An Even Better If would be to allow the Owner to add notes when they republish, and these notes could be visible to non-Owners the next time they open the Dashboard. ... View more

When viewing a dashboard and the filter panel is collapsed, it is near impossible for a new user to find the filter panel expand button. WHY IS IT SO SMALL??  Please update the UI so the filter panel is more intuitive to find and expand. A key feature like this shouldn't require digging through documentation on Sisense's website to figure out how to locate it. ... 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

Currently, when adding a date field as a value in a pivot table, the only option is the # of years/# of days/etc. We need the option to add a minimum and/or maximum date for the selected rows. The current 'work around' for this is to create an integer date, and then use a script to format the integer to present as a date. However, when exporting the data, the date shows as the integer value in the exported data, which is an unacceptable result. Adding the date as a row value solves the export issue, but displays all date values for the lowest level of detail in the data source, which is also an unacceptable result. If it was possible to add the minimum or maximum of a date field as a value in the pivot tables, this would solve all of the issues we currently have. ... View more

I would like to have the possibility for a cube designer to provide a description per dimension. The dashboard designer would be given an help on the meaning of the data he is bringing in his report. The help text would show up on mouse over (tool tips) ... View more

Currently the Usage cube has a dimUsers table that has User Name but it is the email address.  It can be tough to know just from an email address, who the person is.  It would be nice to have the First name and Last name of the user available.  Certainly I could try to make a connector into the mongoDB and lookup the First/Last based on the user id.  But a) I don't want to modify the out of the box usage cube and b) that seems like a lot of work for something that could be added as part of the out of the box usage cube. Thanks, Chris ... View more

Hi It's a need that we have found many times, related to the availability to design the dashboard layput with a dinamic grid, not just columns and widgets in the same column. Users demand more flexibility on the layout design. ... View more

Would like to have the ability to share multiple dashboards at one time instead of 1 at a time. Moving to Sisense from another software and having to share 50+ dashboards is very time consuming. ... View more

It takes 5-10 seconds to load the Manage Cases page in the Support Portal. It takes even longer to open a specific case. A case can only be opened in the same window as the Manage Cases page. To go to another case requires going back to the Manage Cases page first and waiting for it to load again.  Please allow cases to be open in a new tab so that the Manage Cases page doesn't have to be reloaded so frequently, and many cases can be open and loaded concurrently rather than one at a time. Thanks for considering. ... View more

While editing/viewing a cube data source, you can view the logs of the last build, but can't easily see the overall history of builds for that one cube. It would be nice if you could click on the "..." menu and choose View Build History.  A dialog box would pop up showing the most recent 10 builds (or whatever), sorted by date, with start/end datetime, duration, success/failure, etc. ... View more

Hello, On PDFs previews there is different mechanism of showing dashboard. Basically there is now possibility to register any events such 'widgetbeforequery'. Which can lead to incorrect views. The idea here is simple, to add possibility to register and run events on PDF previews. ... View more

Creating security rules within the Data Security menu for Elasticubes only allows you to assign users access to values to that are already in your data. If I am creating a rules for user visibility of e.g. individual 'store references' and a new store with reference '1414' is added, I can't create a rule for store 1414 unless it is already in my data. Could there be an option to manually specify the value, rather than having to select a pre-existing value? (I am aware this possible to add via the REST API, but this is a bit fiddly for frequent small edits). ... 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

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

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

Hello we would be pleased to see possibility to upload custom error pages in Sisense. 403, 404, 500. Also when you will end on not existing page e.g. /app/de. It would be perfect if such pages could also be translatable. It could be set as Look and Feel option or wherever you like.  ... View more