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

We'd like to be able to annotate our bld pods using the helm provisioner. Annotation we're wanting to apply: karpenter.sh/do-not-disrupt: "true" Per Sisense support:  "If we are discussing the -bld- pods, it’s important to note that their configuration cannot be overridden manually. These pods are dynamically generated by the Management service, and the logic for their creation and configuration is embedded within the Management service code. As such, direct modifications to their configuration are not supported." ... View more

Windows Sisense currently has no way for us as administrators to control how much ram is being used by elasticubes. From looking at the community site, it appears that linux has a way to do this through data groups, but when consulting with support, I have been told to increase our resources, simplify our models, etc.   The big problems that we have observed at my company is that 1. Sisense seems to take up the resources it is given - when ram is increased, usage percentage stays at the same level 2. If something does go wrong and resources begin to get consumed, there are no guard rails in place to stop whatever incident is happening from taking down the whole server This second case has happened only a few times in the years we have had Sisense, but I don't like that I have no way to be proactive about these issues.  ... View more

I want an option to remove the "Can Design" role when sharing dashboards (yaml? admin settings? does it already exist?). I dislike the role because: Users don't realise that they're editing a temporary copy, and that the owner can Republish to overwrite. They might make many changes, and then months later someone republishes the owner/master version. I'm not entirely sure if republish always overwrites - if the user has made changes, do they keep their version when you republish or get the new one? If they keep theirs, it makes it confusing when trying to make changes requested by a user, because you make a change, click republish, and then the user forgets to click the revert-to-master-button. Instead of the Designer Role, users can just duplicate the dashboard. That way, no risk of overwrite or confusion.   ... View more

We use the SSO JWT option for Single Sign-on. In Single sign-on configuration, we specify the Remote Logout URL. We want a way to specify this remote logout URL at the user group level. ... 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

Currently in version 0.9 /datasources/{title} is used for cancel all queries but also return a datasource. It is the only way to get a datasource by title. The other alternative is use the get datasources endpoint but the filtering does not work to filter by title.  It would be really good to have an endpoint to get the datasource by title. ... View more

Hi. It would be cool to have a possibility do use external RabbitMQ instead one provided with Sisense Provisioner and hosted in Kubernetes cluster as StatefulSet. We would like to use managed rabbit cluster from AWS. The same case could be for MongoDB with AWS Document DB. ... View more