I use pulse alerts to alert my clients when there is data on Sisense that needs their attention. The Pulse alert emails are accompanied by a big yellow 'Open Pulse' button. This button is the obvious thing to click on, but unhelpfully, it leads to the 'Pulses' tab of Sisense, not the actual dashboard. As a viewer, I want to jump straight to the dashboard, not be confused but this 'Pulses' tab which I most likely will not have seen before nor used. An option to have the button instead open the dashboard directly would be much better and make it much easier to engage customers with the Sisense platform.   I know there is a link to the dashboard on the pulse itself, but going via this screen this is inconvenient at best and confusing at worst. ... View more

With the "Jump to Dashboard" add-on installed & the "suppress _drill_" dashboard parameter configured, SiSense hides the _drill_ dashboards from everyone except the owner (which includes the sisenseadmin account).   As a result, it is hard for the administrator to view and/or manage _drill_ dashboards that are owned by a designer.   There is a workaround via F12 that SiSense showed me, but it's not intuitive.   It would be nice if there was a parameter to allow the sisenseadmin to always have the ability to see/edit the _drill_ dashboards (or perhaps that should be the default behavior). ... View more

While there are some workarounds... * create a user on behalf of the recipient  * create a user that has the email address of an email distribution list * create a forwarding rule in your email  ...many of our users would like to schedule some dashboards to be sent via email with support for a pdf attachment to people who are not and will never be Sisense users in their system. Our application (we're OEM) supports this for reports in the application, and there's an expectation that dashboard emailing would exhibit the same support. As it is clients have to create an application user per external recipient, log in as the user and SSO to Sisense to the recipient available as a dashboard subscriber. In some cases, work can be reduced with an application user that represents an email distribution group instead of an account per user, but even that requires a lot of maintenance from dashboard to dashboard as their recipient lists vary so much. The best work around is using forwarding rules in users' email clients so that when they receive the dashboard subscription, it's automatically forwarded to those external recipients. However, the forwarding process is then tied to a specific user's email account which introduces risk should change need making when they're not available, or the organization.   If the variability of filters and data security is the concern, then perhaps sending in the context of the owner copy is a step toward an answer without meeting the more robust needs of defining different data security for different non-user recipients of the same dashboard.  ... View more

At Splash we have been using report manager for email delivery of reports to external partners. These are outside partners with minimum technical skills and want CSV reports delivered with data. We ended up solving his need using report manager plugin. There are several issues with report manager plugin that we have experienced in last few months and I wanted to understand if there is a different more stable and feature rich option for us. List of issues I am tracking No way for Sisense users to see who is on the email list, other than admins. Only Admins see the report manager tab. I would like users to manage or be able to review who is getting the reports. Email delivery is limited, who gets a report to answer I need to review each job manually. Error notification is never sent to the default email or the email provided in the job setup often due to server failure Intermittent failures with report delivery due to limitation on delivery efficiency or create some retry logic, to queue emails for retry Self serve ability, without buying more licenses how do we enable external partners to have a robust reporting platform where they can self serve. Example when they login they have access to a suite of reports that are canned reports ready to download each day. No SFTP delivery mechanism All report manager jobs appear in a list view, it is very cumbersome to manage I would like to understand how else can I leverage Sisense to build feature rich reporting capability. Let me know if you have a moment to connect. We have our sync coming up June 1st, but we can also connect prior to that. (edited)  ... View more

Current Behavior:  When user selects filter options such as Contains, Does not contain, Starts with, Does not start with , End with , Does not end with etc.  , the resulted suggestions can only be viewed , but cannot be filtered.  Proposal Users should be able to select a filter option, enter a value and use the suggestions to filter.  Currently its giving an inconsistent user experience (Some options are filterable such as Is, Is not,  & few others are not) OR, should display an appropriate label to say the least .  I initially considered this as a bug ,and later realized as a product design.  Thanks ... View more

Currently, when you share a dashboard you can have it email the dashboard out to people following a couple different schedules: Every Elasticube update (with a limit on times per day) Daily (can specify which days and a time) Monthly (can specify which months and what day of the month) The trick is that elasticube updates includes failed updates.  I would like to add an option to exclude failed builds from triggering these dashboard update deliveries. Now that we have alerting for build failures, there doesn't seem to be a reason for dashboards to deliver without new information. ... 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

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

When viewing a datamodel, there's a button to view as "List" instead of "Diagram". I sometimes use that when I need to methodically check each table. When I first open the datamodel the sort is arbitrary, so I click to sort by Name to go through them alphabetically. It'd be handy if it remembered my choice from my previous session. ... 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

It would have been great if there was a quicker way to update the SSL certificates on the Sisense server without having to run the update install. There are clients who do not wish to provide internet connection on the server once Sisense install is complete. As I understand it, if Sisense was installed with internet connection on, then we need to have internet connection in order to re-run the installer successfully. So we will have to make a request to the client to provide internet connection again to run the update install. It would have been good if there was an alternative way to update the SSL certificate.  ... View more

After using the following property in customize JTD widget script for Pivot widget, JTD is enabled for all rows.  drillToDashboardNavigateTypePivot: 1 It would be great if we have an option of enabling JTD for specific rows.  For example, we are having 4 rows and 2 value columns in the pivot but want to have JTD linked to only "row2" and have that "row2" data passing to JTD as filter (as shown in the picture). NOTE: Customize JTD widget script referenced from Official Sisense documentation: https://www.sisense.com/marketplace/jump-to-dashboard/  ... View more

Hello, It would be good to be able to export data to Excel from the Dashboard menu. Currently, one dashboard containing 3 widget requires to go to each widget and export to Excel, resulting in 3 diffrente Excel spreadsheets. Users are requesting to be able to export every widget data into one single Excel file / each data widget in one seperated tab. This features exists in ReportManager, so it is difficult to understand why it is not available from the dashboard view. Thank you and regards, Franck ... View more

Currently, the aggregation function depends on the type of the dimension : - Text or date => Distinct count - Numeric => Sum In our use case, this default assignation is not always accurate as it is sometime required to use Distinct Count with numeric fields. It would be good to hauve the default aggregation function to be choosed by the cube designer, when developping the metadata layer (ElastiCube or Live cube). This way, the dashboard designer will be proposed the accurate function without need to change it. This is particlary interesting with a users population that don't have analytics background and for which choosing the correct agregation function is not obvious. Thank you ... View more

Two problems: Datamodels store old connection information without the user being aware. That increases the chance of accidentally exposing credentials to a different security context. Sisense R&D said that the reason is to show Recent Sources. When you change a dataset, you can end up with two copies of the dataset, which is confusing.   Ideas for improvements (take some or all): Sisense could track the Recent Sources separately. Then Sisense could automatically remove empty datasets. Sisense could show empty datasets under Data Sources in the data model editor UI, and give the user a delete button for them. The Data Model editor could have a drag-and-drop to move tables between data sources. When you click export, there could be a checkbox "Remove data source connection information".   More detail about the problems here: https://community.sisense.com/t5/support-portal/bd-p/SupportPortal?page=casedetails&caseId=500Pk00000Es4PyIAJ and here:https://community.sisense.com/t5/help-and-how-to/models-have-empty-datasets/m-p/20632#M222   ... View more

When filtering on a numeric field and using a Value type filter, I often want to filter on a dynamic value. As the Ranking type filter can take a formula, I would make good use of a Value type filter that also allowed for a formula. ... View more