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

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

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

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

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

Currently, we are using below Rest API to generate a daily report to know the users, groups, roles etc.  /api/v1/users/get We need an additional field (last_password_change_date) for reporting that would tell us when the user changed the password. ... View more

It would be cool if our end users could receive a Digest Email that is sent out on a frequent basis from Sisense. This email would be most relevant if it was based on the groups a user is assigned to already. This would ensure relevant communication, as well as ensure there is control over the reports included in the digest that the user would already have access to them. We would not want the digest email to included recommended reports the user doesn't already have access to. If it was a feature the Admin could turn on/off at the group level that would be our preference. The feature would allow the Admin to select how often the digest went out (weekly, monthly, etc). The feature would allow the Admin to select what content was included: For example:  Changes, Top Used/Popular in the Users Groups (i.e. Org), and then for us I think Newly Published Reports would be ideal.  This would allow an organization to choose whether every time a new dashboard is released the user is notified, for us we would prefer a section in the digest that has these 3 dashboards were released to your group(s).  Other BI tools do already offer this-- Attached is an example of the Power BI digest, as reference. Thanks! ... View more

The behaviour of the From/To date component appears to be causing a lot of confusion new users - we have had multiple reports mis-selecting dates and/or thinking this is a problem with Sisense.   The problem appears to stem from the way the focus is automatically shifted to speed up input of the 'To' date. This is not expected by new users and causes confusion. When a date is selected in the 'From' box... If no date set in the 'To' box, move focus to 'To' box and allow the user to immediately select the 'To' Date If date already set in 'To' box, do nothing. So, the first time you set the date range the first click sets the 'From' date, and you can immediately set a 'To' date with a second click. This is handy, but at the same time confusing if you don't realise what it's doing, and in practice is causing complaints. ... 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

When building dashboards, a common frustration is the lack of ability to multi-select widgets and perform mass actions, such as moving a group of widgets all-together at the same time, or deleting multiple widgets at once. Currently, to do either of those actions, you must do it one-at-a-time on each widget individually. This is tedious and time-consuming if you have many widgets you need to move or delete. It would be nice if there was some way to select multiple widgets at once and perform some kind of mass action on them, like click-and-drag to reposition, or to select "delete" and delete all selected widgets at once. I'm not sure what the best way to do this would be. Perhaps a toggle at the top of the dashboard that allows you to click a checkbox next to each widget. Similar functionality already exists for the main dashboard list, on the left-hand sidebar...a toggle at the top will cause checkboxes to display next to each dashboard (or dashboard folder). Checking any of the boxes will cause additional options to display at the bottom of the sidebar, allowing you to export or delete the selected dashboards. Alternatively, if there were a way to "group" widgets into a container of some sort, then you could perform an action on that container which would apply to all widgets within it. For example, if you had a container, and then three widgets inside, you could select the container and move it, which would move the widgets as well, or you could select "delete" which would delete the container and everything inside it. ... View more

Can we get a "refresh schema for all tables" button? Reason: Our tables are usually "Select * From AnalyticsSchema.ViewName". We control which fields to return by editing the view, not the Sisense table definition. When a field gets added/removed/changed, we need to refresh schema. That's fine to do manually as you're working on that datamodel+views, but we need to refresh all when: We copy a datamodel to a different server. We need to refresh schema at least to double-check that the views are as expected on the new server. (If any fields have changed, then I'll need to go fix any widgets using those fields, or, more likely, update the view to include them.) A view gets edited, perhaps for a different datamodel, and my datamodel hasn't been updated.  I edit several views and want to refresh schema for all those Sisense tables. If I've changed used fields then I'll need to go into each table manually anyway so it doesn't matter, but I've had a case where I've removed unused fields from several views and now I need to click refresh schema on every table individually. ... View more

When a Sisense server's IP address changes, you have to reinstall Sisense. I want a script or button that changes all the relevant settings. We need it because we're planning changes to our network. There are other reasons that an IP address might need to change, e.g. I might restore from a system image backup to a different location, or I might start a new server and, after testing, want to redirect my old server's IP address to it. We'll do it by reinstalling, but that feels like more work than it should be. ... 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

Currently, dynamic/parameterized datasets are not supported in BigQuery connections. You can parameterize the service account information, which is great, but it would be helpful to be able to use a parameter to swap the dataset in the BigQuery connection based on who's currently viewing the dashboard.   For reference, parameterized datasets and schemas are supported by other database engines: Azure Synapse MS SQL MySQL PostgreSQL Redshift Snowflake ... 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

Within dashboards, the only way to know currently if there is a filter on a widget is to open that widget. This is VERY time consuming if there are multiple widgets within a dashboard (we sometimes have up to 10). Please add an icon at the top of widgets (near the pencil would be great). If the icon is grey, no widget level filter is set. If the icon is colored in, a filter is set. If a filter is set, mousing over the icon should return a preview of what the filter is. ... View more

The email schedules have a limitation when the file used in attachment is large in size. Most email servers have a 25mb max limit.  It would be really helpful, if there was an option to include a downloadable link in the email. When a user schedules an email, with the link option, the attachment is downloaded to a temporary path and the link to that path is provided in the email. Clicking on the link should download the file from the temporary path which can be an s3 bucket or from some server. We can keep a retention policy of few days for the files. ... View more

Currently, if we export the pivot as an excel/csv, there is no indication of the date range it was run for in the output file. It will be really helpful to have control on the exported output in excel or csv, such that we can include the date range of the result or other filters applied in the output. ... View more

Upon receiving the warning "Maximum number of series (50) exceeded", the warning does not reappear with a widget, dashboard, or page refresh. Instead, a filter change is required in order to trigger it again. IMO the warning should persist with refreshes and be visible every time due to the impact of the limitation being exceed - data is literally missing from the widget and the widget does not reflect the data set expected by the user.  To that end of being clear about the impact of having more series than the limitation allows, the warning would be best reworded to indicate that impact and avoid users making decisions on an uncontrolled subset of data. For example, "Results limited to maximum number of series (50)..." or "Data limited..." This limitation should also be documented in Sisense documentation, but is not currently. ... View more