Our clients always have limited inventory to sell. What they sell is constantly changing. When forecasting future results, the prediction frequently projects results beyond the saleable inventory. Our clients a neighbor indicator widget showing the maximum capacity for the given product, and then edit the forecast hardcoding the value into boundary maximum limit. However, this prevents the widget from respecting dashboard filter changes that switch between products. Instead, it would be most helpful if the boundary limitations could also be configured as calculated values from the data. ... 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

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

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

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

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

Recently, we were trying to create a widget using the RPAVG function for a rolling 30-day average, which broke our connection to the live model while working (to an extent) on an elasticube. The function worked past the first 30 days on the elasticube, while the first thirty days were (SUM N )/ N. This formula works past those thirty days, but for the first value, for example, gives simply the first value.  A new version of these functions would be greatly appreciated.  ... View more

Currently Embed SDK doesn't provide a function to perform the same function as clicking Restore my default filters button in dashboard filter. It would be great to add it in the future. ... View more

Idea: Allow developers to build/test add-ons in a local environment rather than requiring a live environment. Note that this would be for the purpose of creating custom add-ons for additional functionality that would require testing on the "out of the box" Sisense UI. Background/Context: In most development workflows it is common practice to work on your code locally on your machine and deploy to a local server aka "localhost" to test/view your work in the browser. An example of this is building and deploying a local React.js app to your browser. As you make changes to the code it will recompile locally and update what you see on your localhost. If you're using Sisense out of the box however, to test/view any changes to an add-on developers are forced to upload the files in some way to a live Sisense Environment. This not only limits the innovation of add-ons to developers with an active license and live environment, it makes it painfully inefficient to develop customizations on top of the Sisense application. I understand there are likely some business concerns with allowing the use of the product locally but I'd argue that there are ways to prevent that, such as enforcing some default sample data etc., but in such a way that would give developers a "local playground" to develop/innovate on. ... View more

Hi, Working on a dashboard containing 3 pivot tables. Each have a lot of columns. (see print screen attached). In order to have a proper PDF, I need to turn the page format to A0 / landscape When exporting to PDF at the Dashboard level (from the pdf button top right), I access to a PDF setup, where I can choose the layout (landscape) and the paper format (A0), so that all the columns appears properly. In this screen, there is a Save button so that the PDF setup is saved for next time (see print screen) When exporting to pdf at a widget level, the same setup otions are available (landscape and A0), BUT THERE IS NO SAVE BUTTON. I have to redo this setup each time (see print screen). Could we have the the Save button on the widget / PDF option page, same as we have ar the dashboard / pdf option page please ? Thank you ... View more

It would be great to have settings that allow adjusting the limit of values in a Pivot Table, similar to the existing option for changing the maximum number of columns displayed. Currently, we can only adjust the maximum number of columns displayed in the Pivot Table configuration. This can be done via the Admin tab by navigating to Server & Hardware > System Management > Configuration. From there, go to Pivot Table and set the Maximum number of columns to display We also have a WA for this using a widget script: https://community.sisense.com/t5/product-feedback-forum/idb-p/ideas/tab/most-recent However, it would be great to have it for all the widgets without using scripts ... View more

Our customers want to use the same data field twice within a filter. For example, within the field primary impression we want to include "seizure" and exclude the value "pyschiatric/behavioral problem". Is this kind of functionality on the roadmap, or can we have it added? ... 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

Goal Enable dynamic alerting based on history using formulas Enable reuse of conditional coloring rules for pulse threshold  Background Pulse allows you to trigger off of a threshold (e.g. > 10,000, <= 10) Conditional Coloring of widget values allows for functions (e.g. Min([Months in Date], [# of unique Transactions]) Perhaps the Automatic anomaly detection does this, but we have no visibility into what is results in an anomaly.  Also not sure if you have to wait for the anomaly detection to learn. e.g. the cube has been built every day for years and has years of data, but the widget was only created a couple weeks ago and the pulse alert was added yesterday.  Will it detect anomalies or out of bound conditions that we could write with a formula Desired Functionality Enable use of functions in Pulse thresholds similar to Conditional Coloring of widget values Ideally enable reference to the Conditional coloring options for the widget.  The dashboard designer already built it into the dashboard. The user just wants a pulse alert when the widget turns RED.  Provide means of selecting from existing conditional coloring rules (Whether they are static values or forumlas) when building/editing the Pulse tile. ... View more

We find our clients sometimes using the widget information (i) button to provide their users with context for a widget. Their users sometimes click the button in search of information even when the designers haven't added any text to the widget information button. It would be helpful for end users to have a way of knowing before clicking that the widget information does or doesn't have additional information about the widget. ... View more

---Summary:--- When you jump to dashboard, your dashboard filters are carried over to the destination. I want to also carry any Drill Into breadcrumbs. ---Example / use case--- I right-click on a FieldA row in my PivotTable and drill it down to FieldB. Then I click on a number to Jump To Dashboard. The destination filters for the FieldB row I clicked on, but it doesn't filter FieldA. That's fine when FieldB.value occurs only as a child of FieldA.value. But some of my FieldB items are repeated in several FieldA items. For example: Many cities have a "Main Street". I right-click and drill-down on New York's street names. Then I click on data for Main Street to jump. The destination dashboard will show data for every Main Street in every city, instead of just New York's. --- Can you make JTD respect such a drill-down? --- PS: I also made a request about making Drill create dashboard filters. That would partly solve this request, but not fully: Sometimes, I don't want Drill to create dashboard filters, but I will still want the Drill to be respected by JTD. ... View more