I would like to see some improvements regarding the pivot table in Sisense: Measures as rows Right now, when you add multiple measures to the pivot table they are automatically added as an extra column. Every major player in the BI business allows for measures to be added as rows, I would like Sisense to do so as well Expandable dimensions (could be used for almost every widget type) Let's say I have a pivot table showing revenues with categories as rows and years as columns. Ideally, I would like these to be expandable, i.e. if I click on the + icon for years, it should show me the quarters, months and so on. This could also be implemented for line, bar and column charts.  For categories e.g. I would like to expand to sub-categories. The drill-down we have right now doesn't work, it zooms in on just 1 category losing an overview of the data.    ... View more

Currently, the "Upsert" build behavior is only available for Build to destination. It would be great if we were able to utilize this feature in our Elasticube model where we are not building to destination. We have numerous tables containing created date as well as updated date that are attached to an id field but are unable to use the updated date field since this will bring in duplicate (or more) rows per id which we can not have. Ranking duplicates and filtering out is not a sustainable with the size of our datasets. The ability to look at the id and updated field would solve this issue without the need for a complex workaround in our data source (Big Query). Thank you! ... 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

When Pivot or Table widgets, the options for formatting a datetime column allow showing the date OR the time, with no option to show both together (e.g. if format was "dd/MM/yyyy HH:mm:ss" then we could get "23/10/2022 17:05:21").   ... 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

While it is possible to Lock a filter so that users can't change it, sometimes they get confused by the presence of that filter and want to try to change it, which results in a support call to us.  There could also be times when the filter criteria itself is sensitive. We should be able to right-click on a filter and choose "Hide from Viewers". This would also have the benefit of cleaning up the user interface a bit, so viewers don't have to wade through criteria that they can't control anyway. ... View more

It seems strange to me that each time I need to add another table to my model, I have to re-enter all the connection (or pick a recent connection). If i have 10 tables in my model, they all have their own individual connection information. If a server name ever gets renamed, it'll be a crazy headache for us. There should be a place where you define the distinct list of actual database connections (one per server or database), give it a name, apply security, etc. And then when you go to add a table to a data model, at that point you pick from the previously defined available list of connections. ... View more

For users who wish to receive their Dashboard contents using the Subscription service, Sisense supports embedded emails or PDF format only. For convenience and expedience, I would like to see support for users to receive compatible Dashboards (e.g. Pivot Tables) directly as an Excel attachment. This will help for users who wish to receive regular emails containing important data in Excel format for integration with other systems.  ... 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

Hello, Currently, when we want to add a recipient to a new dashboard schedule, the dashboard has to be previously shared with the recipient. If it isn't, the recipient doesn't show up in the autocompletion list (emails - users name). In that case you need firstly to go back to the dashboard, share it with the recipient, come back to ReportManager and finally, add the recipient to the new schedule. This is confusing to our users who in such case consider this as a bug. => New behaviour wished :  When you add a recipient to a ReportManager schedule it automatically shares the dashboard with him. Which makes sense since if you want to send a dashboard to a user, it implies you want to share it with him. ... View more

Required feature to auto manage the license when on SSO. So that if a user drops out of organization or has not utilized the license in the last x days, Then the license is auto recovered from the directory and is free to be consumed. If it possible then please required document  with us. ... View more

Hi, Actual access to Grafana monitoring tool is under Server & Hardware > System Management where are a Monitoring and Support option in the main Admin option.  It's not very intuitive now. Best ... View more

I have a data model with lots of tables (more than 30). That makes the UI painfully slow, e.g. when editing relationships. I think the reason is that it’s calculating where to place them on the screen. I’d like to request an alternative, crude interface that doesn’t slow down for lots of tables. Or make it work for lots of tables – e.g. do the positioning calculations when first opening, but not each time I resize or click on something. ... View more

In a pivot table, I want the ability to display a certain number of values for each grouping.   For example - I want to see the top 5 Cities by Population for each Country. Currently, I would need to fitler individually on each country to see that, but I want my pivot table to have all Countries and each of their 5 cities as the next level down. Currently, Sisense only lets me see 5 cities total and their corresponding country, not 5 cities per country. ... View more

At the moment, the caching period of live models is set for the whole instance which removed flexibility where you'd want the caching period to be different for exceptionally large models.  For example, we have a table we have to ingest via a live connection as it is too big for elasticubes - but wouldn't want the caching period for this live connection to be too "low" as it would cost a lot via AWS.  However, we would want a low caching period for low latency reporting ... 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

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