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

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

Bug Click Edit on a dashboard filter that is near the bottom of the screen. The edit filter dialog pops up, but the OK button is off the bottom so you can't click it. Scrolling doesn't help. The only way to fix is it to reposition the filter so there are other filters beneath it (but then those get that problem). Applies to Sisense Windows 20.24.3.10115. In Sisense Linux, the edit filter dialog positions itself in a way shows the OK/Apply button even if you clicked on a filter at the bottom of the screen. ... 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

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

Hi, I have issue with setting two date dimensions in dashboard. The goal I want to achieve is to have a history of records, which are also have it's own date dimension. You can download model and dashboard. I would like to have difference in growth ower selected period for defined dates. For example 2 days ago I sold a car for 1000, and yesterday the proce have changed to 1500. The sale date is for today. So the growth over 2 days is 1500, and for 1 day 500. Additionally i would like to compare those values to previous year, and go back with both date dimensions. Tricky part is also, that if there is not sale for this year, PastYear() wont count prior year. I tried to play around with filtered measure plugin, however it doesn't give me exactly what i want. Do you have any suggestions how can I approach such data and 2 date dimensions? Thanks 🙂 ... 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

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

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

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

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

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

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

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

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

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

Hi, I have gone through your connection update process for live models. But As I discussed with sisense team, they don't have any single API for updating connection. As per current scenario we need to follow multiple steps like below:- 1. Get table by: GET /datamodels/datamodelId/schema/datasets/datasetId/tables/tableId. response => tableResult 2. Override table by PATCH /datamodels/datamodelId/schema/datasets/datasetId/tables/tableId} where body = tableResult from the step 1. Only after performing the above steps, you can use PATCH/datamodels?/datamodelId?/schema?/datasets?/datasetId to update the schema for this dataset. So I just want to proposed one idea here that we can use multiple option here like below:- 1. We can provide any Key Vault connectivity for each model where we can store our connection details and we can use them for our model connections. 2. We also can provide a single API where our connection can we updated for all relevant objects & model it self. ... View more