When the sisense user is deleted the email of this user is still in the recipients list for a report in the Report Manager. If the report Manager is configured to send the reports to external customers, the user who is no longer with the company will be receiving the reports with dashboard data as the reports for the external users are generated using the owner or an additional user. Thanks. ... View more

NOTE: This is based on a post I made in the "Help & How To" forum. It was recommended to me to make a post here, in the Product Feedback forum, about it. There should be a way for Sisense to display the currently-selected filter values directly on the dashboard. I know that users can see this by expanding the right-hand sidebar to see the Dashboard Filters, and it's also a display option when you export to PDF. However, these aren't always obvious or available to the intended audience for the dashboard. For example, if I have a dashboard that's setup with a dashboard-level filter for "Work Group", it would be nice if I could display - directly on the dashboard itself - what work group is currently being filtered down to. Also, some of the values can be unclear, especially for date filters that use colloquial language such as "This Year" or "Last Quarter". There should be some way of displaying the exact date ranges that are being filtered for. For example, if today is November 13th 2024, then the "Last Quarter" filter value would mean dates from July 1st 2024 through September 30th 2024. But after the new year, if I were to check the dashboard again on January 6th 2025, then the date range would instead be from October 1st 2024 through December 31st 2024. Currently, in both cases, it'll just still how as "Last Quarter" and it's up to the user to figure out what that means (which can be difficult if they're looking at a static printout from some unknown time in the past). Other time periods can also be ambiguous or prone to misunderstanding. For instance, it's common to see people assume "Last Week" means a rolling time period covering the last 7 days, rather than the prior calendar week. Or assuming "Last 2 months" means the same as "this and last month", rather than the prior two calendar months not including the current month.  ... 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

The Data Security tab's group/user assignment window currently has a max search limit of 20 results.   The "results" search limit should be configurable because we have approx. 50 groups that need to be assigned, & it is very difficult to find/assign/manage all of the groups when the search window does not return all of the appropriate results. ... View more

We have a use case where we need a Viewer role to have the ability to import and share dashboards. The problem is that those elements are set to canBeOverridden: false. Please change share and import to canBeOverridden: true for the roles API. ... View more

We disabled the new Simply Ask option in the Sisense configuration but it's still showing as a disabled option when you click a dashboard's context menu. We submitted this as a defect but were told that it's "by design". It's by design to show an option that's been disabled? We don't want users to request the option be turned on, as the hover text suggests. ... View more

Would you consider allowing the retrieval of files from the nodes with the file management so that end-users can retrieve logs with having ssh access. ... View more

Hi, We are having several issues when dealing with Elasticube Builds. We can now schedule the build (both UI and REST API), but we have no tool to monitor and control this key functionality. What's the history of the builds for a cube? When can we see the whole picture of the time each build for each cube happens to optimize resources and find concurrent builds in time? Now we can just see the last build log, as an isolated entity. We cannot monitor all the builds as a whole, to see the whole picture of all the builds (when it happened, how many time it got, etc.). As administrators, we have no way to control now this. Even we cannot check the history of builds for a cube. It's a critical feature for administrators.  Best ... View more

Hi Team,  In Support Portal we can have a lot of tickets raised and some of them are in Sisense side and some on our side.  Will it be possible to retrieve the info if a ticket is waiting from us or from Sisense directly in a list view ?  Thanks  Bastien   ... View more

Hi, for this moment we have such a behaviour: sum(NULL * 10) = NULL but SUM(NULL * [id]) = [id] in the same time if [id] have values (1,NULL) and we will do SUM([id]) = NULL Is it possible to add some toggle in the system how to work with NULL values. For example, if it is disabled it works as NULL is empty and SUM(NULL * [id]) = [id] But if it is enabled, so all NULL should be works as in mathematic SUM(NULL * [id]) = NULL etc ... View more

As of L2023.3, in Sisense’s Helm Charts , “Tolerations” are supported by the micro-services. It prevents end-users from configuring “Taints” on the node that they want to dedicate to Sisense. Since no “Taints” are configured, so all nodes can become eligible to host Sisenses’s pods. They experienced that scenario when pods from some other application services were scheduled on a Sisense node. Would you please consider allowing the pods to be protected not only with  “Toleration” but also with “Taints”. The justification for this is that, even though it is mentioned in prerequisites documents that Sisense should be installed on dedicated servers, there is a non-negligible factor from the customers perspective that is the overhead administrative costs, especially for customers who must already manage numerous clusters for several applications, multiple environments, and redundancy.   ... View more

I have a client that has SSO users and non-SSO users.  On Sisense advice, we have created a separate tenant for the non-SSO users.  We expect that those users would have all user email features of users as if SSO did not exist on the system.  We are finding that the new user invitation email is not enabled for these users (among other email functions).  Therefore, these users are not able to set their passwords when they are created.   As a result, we are using a common password for 600+ users.  This is obviously not satisfactory.  Those tenant users can now log in and change their password, but we have no way to enforce that they do this as we would with an invitation email.   R&D has told us this is the expected behavior (refer to case #00746676).  This behavior is not working well for my client.  I would like all user email features enabled for non-SSO tenants. ... View more

At the moment, you can do row filtering in a Data Model, by applying an enforced filter.  This works fine in simple scenarios. In my case, I have 150 different users who each need to be able to see only their own data.  So I have to add them one-by-one to the data model's "Data Security" area.  Not only that, I have to do this to 10 different cubes, so this will be a lot of manual effort to set up and maintain over time as people come and go. What I'd like to be able to do is define a custom attribute on the User record, like "Location ID".  I'd fill it in for that user, entering "12345" for a particular user record.  That User is also a member of a group called "My Restricted Group". Then, I could go into the Data Security section, add an entry for the Location ID filter, applied to "My Restricted Group", and reference the "Location ID" number.  Then the system would enforce it at runtime -- is the logged in user a member of "My Restricted Group"?  If so, apply a fiter on the Location ID field, and fill it in with the value in their User profile. Then I only have to maintain the Location ID value in their user profile once, and only need to apply that Location ID filter once per cube, not 150 times per cube. ... View more

When login as Admin, under ReportManager page, there is a setting button (the wheel at the top right side) that allow to customize the user UI experience. i.e. toggle in/off options : - archiving - priority - event based - csv export ... I would suggest a setting here to toggle on / off  "Apply customer filters" and button "Edit Report Filters" just like the other options. Thank you ... View more

We have configured Pulses that send through Webhooks to a Slack channel when certain elasticubes fail. This is a really helpful feature, BUT it would be even more helpful if there were the option to also send the error message along with the failure message so that the reason for failure displays in Slack. ... View more

Currently, when using the Usage Analytics EC you do not have the ability to audit for everything you need when it comes to what your users are downloading.  Right now all we can audit for is PDF, Image, and CSV.  I would like the ability to be able to audit for Excel, PPT and any download options that are made available. Management wants to know who is downloading what, but right now we can only give data for some items and only for 30 days.   I would like to be able to have a larger selection of items to audit that utilize a customizable timeframe for how long to retain history for a select data point. If we are to audit for a pattern of downloads 30 days does not meet our needs.  Currently, if we want to audit for more than 30 days, we would need to get the data in a format that can then be loaded into an external DB that can then be reincorporated back into an EC for reporting.  This seems to be a waste of time and resources when this should be able to happen in the source system. ... View more

Please enable the possibility of selecting a default CSI (storage class interface)  from a set of existing CSIs so that it may be used as default Sisense persistent storage option. This is is a necessary feature for persistence of storage in cases such as autonomous cluster scaling or rebalancing, as well as disaster recovery.   ... View more

Some end-users have several environments where they must provision Sisense and they strive to standardize and automate the processes as much as possible for efficiency. It would be great to be able to extend standardization and potential automation of configuration to the Helm Chart level: Please include some ways to enable feature or disable feature with the helm chart so that if we want to enable file management everywhere we could provide a value to all our helm charts so we can have uniform configuration. ... View more