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

We create a basic set of pre-built dashboards that we publish, where business users can view but not modify.  We also have two-tiers of analytics offering for business users (standard and premium).  On our common, pre-built dashboards, which are available to both standard and premium, we would like the ability to expose Simply Ask to only those users of premium (hiding it from those who are standard).   While this may be achievable via a 2-model, 2-dashbaord set approach, we desire to manage a single set of dashbaords and model to simplify deployment overhead and maintenance. ... View more

we have "label" field that have multiple values per entity and would like to be able to use the same field for both column and row in the pivot table. We will use different filter on column vs row so different values will be shown ... View more

We've been asked by customers for the ability to view more results than the current max of 10 ("showing first 10 results") when hovering over a data point in a scatter map. ... View more

It would be better to have more control options over exactly when the email report for a dashboard is triggered out to users. Currently we use the option "Every Elasticube update. No more than 1 emails per day" but that has issues: 1) We would only like the email to send if the Elasticube update is successful, rather than every update (including build failures). Otherwise we send a report out with missing data. 2) The rule of "No more than 1 emails per day" doesn't seem to be working properly. Meaning if we refresh the Elasticube more than once per day, users are receiving duplicate reports. ... View more

It would be nice to allow a Widget to be viewed in full-screen when embed=true. If it could just fill to the size of the iframe that would be better than what it currently. ... View more

Currently Notebooks provide a powerful opportunity to access and visualize data utilizing SQL and to add these to fusion dashboards.  Fusion's primary analytics environment allows for powerful dashboard-wide filters.   Currently dashboard filters do not apply to charts or tables which are created through notebooks even if the notebook is pointed to the exact same data table and column as other dashboard widgets.   Please develop the ability for dashboard filters to filter both fusion dashboard widgets and also notebook-based widgets.   ... View more

We want to be able to see certain metrics by day of the week on bar chart to detect certain patterns without adding a separate day of the week field for every date stamp into our data cube.  ... View more

Is there a way to retain formatting when exporting to Excel? We currently highlight rows in red if they meet a condition, but the formatting does not carry forward to Excel ... View more

Enhance the Header options when you download a widget as PDF (via ellipsis > Download > Download as PDF) to include the same options as when exporting a full dashboard as PDF. Dashboard PDF export offers "Date As Of", "Dataset Name" and "Dashboard Filters" in the Header options (attached). This is also needed when exporting specific widget, which only offers Title. ... View more

When using Sisense Live Models, the lowest level of granularity when visualizing date-time data is “Round to 15 min”, not at the minute level. Versus, when using Elasticubes, the most granular option is every minute. It would be incredible helpful for us to have granularity at least to 5 minutes for Live Models because we are working with IoT data that we want to visualize. ... View more

This scenario is for embedded Sisense. When creating a new widget from scratch, it seems like the new Widget wizard selects either an Indicator or Pivot Table type of widget depending on the nature of the data being selected by the user. More often that not, this is resulting in a Pivot Table being the automatically selected widget type. Often times, our users do not need to use Pivot Tables; and since Pivot Tables are computationally more expensive to generate, this results in us incurring unnecessary expense for compute on our data warehouse. I don't want to block Pivot Tables -- I just don't want them to be default widget type. I'd rather Sisense use Table as the default widget type; and/or allow Admins to define the default widget type. ... View more

Currently every BloX widget has its own stylesheet that is defined separately from the look and feel of the rest of the Sisense application (apart from the action buttons, for some reason).  This is understandable for some out-there cases, but in many cases I've had to work with Blox, what I really want is for my Blox widgets to fit in with the look and feel of the rest of the dashboard -- in essence to use the same default stylesheet, if not as the whole dashboard application, then at least as other BloX widgets. The current 'stylesheet' in the widgets could then be used to overwrite any details for that particular widget, instead of it functioning as a full stylesheet every time. Thank you! ... View more

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

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

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

Sisense charts show tooltips when you move the mouse above them. When showing those tooltips the website automatically formats numbers in the tooltip in order to simplify the reading and shrinks those numbers if they go above 10k. Most of the times this is what I want as a user, but not always. According to my observations, tooltips stop showing the real number and show a simplification when it goes above 10,000  (e.g instead of showing 16742 it will show 16.7k). This idea would be to allow this number to be displayed in full instead of the shrinked version. Sometimes it is just useful to see the real value and not the simplified one. As a user, I'd like to see the real one sometimes. There are two possible ways of implementing this that come to mind, in the Tooltip section when editing a graph: Add a checkbox, clickable, with the current behaviour by default "[ ] Show raw numbers". This would be below "[ ] Show Total in tooltip" Add a threshold numeric input so that users could manually specify from which number onwards the formatting would shrink (e.g 10,000 by default).  "Shrink numbers above: [            10000]" First option is simpler to understand, second one is more flexible.  Right now, the workaround I'm using is to Edit a chart, then click on "Output" in order to see the real numbers as a table, but this is inconvenient. Here is an example of the number I'm referring to, in a chart. You see 15.9k and I'd like to see 15935.   ... View more

When creating widgets using the day of the week as a category, the categories are sorted alphabetically by the day of the week (Friday, Mon, Sat, Sun, Thu, Tue, Wed) instead of sorting by the actual order of the days of the week (Sun-->Sat, or Mon-->Sun). Seems like an obvious, and absent, feature. ... View more