It would be great if we were able to setup Active Directory for an individual tenant while having SSO enabled for another tenant. This would help us differentiate between our external customer facing and internal BI. ... View more

Instead of having to manually set the same format for each date type over and over, it would be nice if you could set defaults for each date type (Year, Quarter, Month, Week, Day) somewhere and have everything default to that with the ability to change away from the default if needed.  This could be done in the same area we set First Day of Week and Fiscal Year for the server. ... View more

1. View all history of builds and its corresponding logs from the cubes. Because, I could not see the last build failure reason, if another build got started. I need to wait for another build to complete or fail. 2. View all history of changes and provide a way to revert as in Google docs for both the cubes and dashboards. Some times, if something went wrong, we should just be able to revert to the previous version and continue from there. 3. Provide a way to view the list of cubes in the queue waiting for the build. Also, allow remove or disable them for a period or rearrange the queue to build. This will help in prioritizing something manual on demand. 4. If a cube build fails due to the memory or other configurations issue, provide suggestions like what has to be changed and based on what before triggering another build. 5. Provide a page to derive the suggested the configurations like memory, cpu, timeouts etc by collecting details like 1. Number of cubes, 2. average cube size, max cube size, min cube size, or number of cubes by size range say <5g, <10G, <20G, <40G etc.., 3. Frequency of the build per cube etc.. 6. Provide a page to view all the slow running dashboards, slow running queries and some suggestions to improve it. 7. Some times, if a dashboard got changed and republished, it is not getting applied to all the users. Provide a way to view the version of the dashboard the user may view. 8. Between builds, if there is not much change in the data, Sisense build should go faster. Provide a way like one common place to build each table from other sources individually and keep it ready. From there, if we build say functional cubes, it should build in flashing fast using the locally stored data. I see the cubes are pulling the data faster from relational db but very slow from mongodb. Now, if we are pulling data from another sisense cube or from the source no big performance difference. 9. Also, I am not sure, if we are restarting the nodes, should we necessarily mark the cubes in queue as failed, instead adding back to the queue as it was before the restart and just marking the actual cube got failed should be good enough. More later .. Thanks, Muthusamy J ... View more

In browsers, usually links can be right-clicked. You get a menu including "Open in new tab" and "Copy link". Some Sisense links block this behaviour: e.g. the list of dashboards and jump-to-dashboard links. It'd be nice to get it back. To be clear: I do not want every link to open in a new tab. That would be annoying. I just want the option to do so. For example, here's a link where the right-click does work:   ... View more

When opening a support ticket, it's required that a large form be completed. Among these is the Sisense Account Type, Environment, and Version. We too frequently open a support ticket only to be provided with a response unrelated to the information provided in these fields (e.g. a Linux based recommendation after specifying the issue is occurring in a Windows environment and being asked for a version number after the information was already provided). Given the global distribution of Sisense support resources, it can already take a day before expecting a response, but for that response to then be unaware of the information provided in the ticket details causes delays, extra rounds of communication (especially when our support rep doesn't realize that the Sisense response is for the wrong version), and frustrates our support teams and the clients they in turn support. And we imagine the Sisense support reps don't love finding they sent irrelevant advice and don't like seeing our support reps' confusion when they aren't already aware of the information provided in the case opening form. We appreciate Sisense support reps and want to see them support us with as little friction as possible. Thanks. ... View more

As an admin, have an option at the top of a dashboard to be able to view it as another specific user.  For example, if user John Smith is set under the data security on a cube to only have access to rows for a certain region, the ability to view a dashboard as John Smith would make checking user access very easy. ... View more

We have created many folders (and subfolders) to help us organize our dashboards. It is currently very cumbersome to share folder access and ownership, which must be done for every dashboard within the folders. It would be nice if there were an easy (and native) way to share access to a folder and every dashboard within it, or to change ownership of a folder. ... View more

Currently, builds can only be scheduled in the UTC timezone. This is confusing for someone not in UTC and when you have to coordinate with external processes. The user should have the ability to schedule builds on their own timezone.  ... 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

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

There needs to be a way to deactivate user accounts rather than completing removing. We have users that will no longer have access to the system, but could come back later (for example, trail users). The workarounds are currently: reassigning security groups (means those users are still taking up licenses) writing our own user admin functionality (only makes sense if we are integrating users to another platform) Adding a 'Status' or 'Disabled' flag to the user account would accomplish this. ... 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

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

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

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

Simply put, the ability to have a button within the UI for when new users are created within a particular data group (or similar category) to replicate permissions, DS, dashboard sharing, pulse, data model shares, etc.  Even simpler, the ability to have a column within User Mgmt. to show which dashboards are shared with which user.  ... View more

Currently there’s no way on the Sisense UI to have an overview of when the next ElastiCube Builds are set for. Having such info available would make it possible to easily select relevant time slots to run load testing scripts for instance, but also more broadly to help understand and finetune the current Builds orchestration. In order to do so, we would like for admin roles to have access to a single table-like page that would list all the Builds scheduled in the next 24 hours with the following columns: ElastiCube name Build start date Build theoretical end date* Last successful Build duration * Build theoretical end date = Build start date + Last successful Build duration * (or NULL in the rare event where the Build has never succeeded before) Additional features: CSV Export Sort option on column headers Pagination Note: a single Elasticube can have more than one entry (in the example below, we assume the admin user opens the page at 3:00 PM and the ElastiCube_B's Build is launched every 2 hours). ... View more

Hello, Currently the number of queries running in parallel during an EC build is set at the server level. With setting "Build / Base Table Max Threads" (4 by default). The optimised number of simultaneous queries is very much dependant on the context of the EC. For instance, an EC with 4 differents date source is more likely to accept a high number of simultaneous queries (spread over the 4 data sources), than an EC with only one data source. Therefore, I would like to suggest to make this setting per cube instead of at the server level. An alternative would be to have this setting at the Data Group level. Thank you and best regards, Franck   ... View more

Would like an easy way to transfer ownership of objects to someone else.  Or for a super-user admin to be able to "take ownership" of a data model or dashboard.  Will make it easier to deal with when someone leaves the company and they owned things in Sisense. ... View more