We have a few dashboards where the displayed data is only valid when a SINGLE ITEM is selected for a filter. We want to have the standard dashboard filters that our users are used to, but we want to prevent them from selecting more than one item at a time.  In the attached image, we want the red highlighted areas to be disabled (not selectable) for non-owners/non-editors of the dashboard.  We should be able to publish the dashboard with a default value for the filter and allow them to select a different value, but not multiple values.  ... View more

When using Sisense as a Viewer, I would like my users to open a widget in Full Screen mode and interact with the Filters. At this moment, when opening in Full Screen, all Filters are locked, preventing the user from interacting with them.  ... View more

When viewing a dashboard and the filter panel is collapsed, it is near impossible for a new user to find the filter panel expand button. WHY IS IT SO SMALL??  Please update the UI so the filter panel is more intuitive to find and expand. A key feature like this shouldn't require digging through documentation on Sisense's website to figure out how to locate it. ... 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

We have some ideas for enhancing Pulse: Once a Pulse alert has been created, have the ability to edit the filter from the Pulse page. Have the ability to create Pulse as an option from the entire dashboard.  Users would select a measure for the pulse and set filter conditions from the model in question directly. Make the Pulse input pop-up available within the application for developers (e.g. 3rd Party) to exploit from plugins they have developed. Add ability to configure Pulse to trigger on a schedule (once per day, once per week, etc.), e.g. when a build is done, the alert gets sent according to the schedule. Option to set Pulse to trigger when value changes in any direction rather than having to set up a specific calculation. ... 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

We have tried increasing the row limit for CSV download of live models to 250K rows but Report Manager is still limiting output to 5,000 rows which is the query setting of live models. We would appreciate a specific setting for Report Manager that determines the number of rows or have RM use the row limit defined for the report type (in this case CSV and 250K rows). Changing the query limit for the model does impact the report manager, but this impacts all users and every UI interaction, so the data retrieval volume explodes. There should be an independent setting related to report generation. ... View more

It's the standard in our industry that products are on sale only for a limited time. For example, tickets being sold for an event aren't sold after the event has occurred. But there's not way to forecast future sales and prevent the forecast from predicting sales after the event has passed and no sales can possibly happen. Instead, customers have to edit every forecast that is currently predicting beyond its event date, every day, to predict only the correct number of future periods.  We'd like a way to predict N future periods, but not past a point in time at which inventory is scheduled to be no longer available. ... View more

When you duplicate a widget in Analytics, it automatically duplicates next to your current widget. If you already have multiple widgets in that row (which you've spent time sizing to give a nice appearance on the dashboard - and they're not just distributed evenly on the row), the new widget then resizes all the previous widgets in the row so it will fit onto the row. When you then move the new widget to its own row, the widgets on the previous row have to then all be resized to get the sizes you wanted again.  Some options for different experiences... Option to duplicate widget to bottom of dashboard Option to duplicate widget to "new row" which puts the new widget on its own dedicated row below the row from which it's being duplicated When a widget is duplicated on a row, and then moved out of that row, maybe the remaining widgets could redistribute back to how they were prior to the duplication ... View more

I would like to be able to run a "lineage/dependency" report in Sisense. Something that will tell me for all the cube/live data sources: - Data source name - Type (cube/live) - Dates of the data model (created, modified, last built) - Data sources being referenced and type (web service, database, etc.) - Details of each data sources (SQL Server, servername, database name) - Tables or objects being referenced by those data sources It's important for managing the environment to know what we are using, or have an easy way to know what data sets/dashboards would break if a table's structure were changed in the database. ... 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 appears that once you've created a cube or live data set, you can't rename it. You can duplicate it, but I'd really like to rename some of our models without any of the associated dashboards breaking. ... View more

Bar charts show the bars sorted in order by their label.  Sometimes you want the bars to be in ascending/descending order by their sizes (i.e. the value being measured), so that the most significant items are on one side or the other.   While we're at it, the option in the bar chart design to Limit the number of bars being shown to just the "Top X", would help where you have situations where again you want to focus on the most significant items (smallest or largest) without outliers throwing it off. ... View more

Looking for a way to change the logo based on their corresponding theme. We can create themes for the different companies but there is no option for logo in the Theme and would like to capability to extend the white labeling past just 1 logo ... View more

When we access the widget data directly(Here we are fetching data from JAQL call itself and are not fetching data using CSV request to Sisense) then it shows N/A instead of a blank string(where the value is NULL). Is there any way where we can get a blank string in place of the N/A which is being shown to represent a Null value? ... 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

The idea of this is so you could show the elasticube data on the primary axis, and then potentially low latency data on a secondary axis - allowing easy comparison of live vs historical data ... 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