Because a non-trivial amount of the population is colorblind, it's a best practice to never rely solely on color when indicating behavior or status of a UI element. The filter-pane buttons are by default, I think, green for positive selection, red for exclusion, and grey for unselected. It would be better if there was also a small icon in the button that would indicate checkmark if positive, "X" if negative, and blank if unselected. Or perhaps, if Unselected (red), show a thin "X" over the whole body of the button. Thank you. ... View more

We support multiple applications of data within a model, as there is crossover between the applications; however, our customers have granularity to choose which application data with which they are allowed to see when they create new dashboards. We use column level security for attributes today so that Application A author can only see table of data pertaining to application A while Application B author can only see tables of data pertaining to application B (note that a user can have both author rights and see all both application data). We found that this does not pertain to Shared Formulas.  This now increases the "noise" that authors see, as they are seeing formulas for an application that isn't something they can readily use. ... View more

Currently sorting of dimensions/categories/series is by Ascending and Descending only.  There are times when such data points need to be sorted in a non alphanumeric manner.  For example, Critical, High, Medium, Low is the desired sort, but this appears as Critical, High, Low, Medium or Medium, Low, High, Critical which looks sub optimal to the user.  A workaround is to add a number prefix via modelling, again this is less than ideal for the user, as is a script to update the displayed values to remove the prefix.  As is possible with other BI Tools, there should be an option for the Designer to configure the sort.  There are various community plugins and scripts that do this on an explicit per widget basis, however these are prone to fail/break and aren't guaranteed or supported through version upgrades.  This should be a part of core application functionality. ... View more

As a standard offering, enable color conditions to also be displayed in the Grand Totals columns/rows. The coloring should also carry through to Excel or pdf downloads, the same for the rest of the pivot table.  Current custom script solutions are at risk of breaking with future version updates, and the Grand Totals colors do not carry through to Excel and pdf downloads. ... View more

Currently, it appears that Shared Formulas are displayed in the selection dialog based on the order they were created. It would be great if they can be arranged logically, or at least sorted alphabetically, otherwise the list can grow to become disorganized and difficult to use. ... View more

The idea here is to expand the formula editor (Specifically CASE WHEN Statements) to allow the creation of dimensions or "buckets" based on filtered data. This is useful on the dashboard level as we may want to recategorize our data dynamically after filtering the dashboard.    Lets say I have a pretend table holding daily customer transactions. In my report I'd want to see each customer's average spending for an arbitrary time frame. I'd also like to categorize that player BASED off that average spending. Which could change based on any filters I use.  IE)   CASE WHEN [Avg Money Spent] > 999 then '1000+' WHEN [Avg Money Spent] > 699 then '700 to 999' WHEN [Avg Money Spent] > 399 then '400 to 699' ... WHEN [Avg Money Spent] >= 0 then '0 to 99' ELSE NULL END   I would then use this calculated dimension in visualizations like pie charts, etc. I'm not sure if this is possible, but being able to use this dimension as a filter would be very useful as well. IE) Show me all the customer who fall under '400 to 699' range for any given period. ... View more

Problem: Users commonly wish to share data with their team members, but reports with many filters can be difficult to reproduce and share with others while abiding by security permissions. This causes confusion when numbers appear different, but the result is simply that the users are comparing data with two different filter sets applied. Summary: Saved searches would allow for users to create filter sets across multiple dashboard filters to quickly return to a filtered view of data. These saved searches would also be highly beneficial if it allowed users to quickly share these filter sets with users that have access/permissions to the dashboard of origin when the two users are both part of a user group that allows filter sharing.    Admin User Story: As an admin, I would like to create a saved search that allows users to see data for each region of the United States for the current year-to-date as well as saved searches for each quarter of the current year. I don't want to create multiple dashboards or even multiple widgets as I'd like the user to be able to see consistent stats for each time frame.  The admin creates a saved search for each of the desired filters to allow a user to quickly navigate and select the different saved searches to populate multiple filters at once with the desired filter set.  The admin has access to share with all users, but they decide to share the filters with the Executive user group. In order to share with the executive user group, the admin must enable filter sharing within this group. The admin as well as members within the executive user group will be allowed to share with all members in the executive user group once this permission is enabled.  After enabling filter sharing, the admin shares the filters with the executive team. The admin can choose to include an email or only share within the system with no notification. They decide not to notify all users of the group, but they copy the share link for the 3rd Quarter Western Region saved search. They send an email to the director of the West Region with the saved search link. (See Viewer User Story)  Viewer User Story (West Region Director): A viewer belonging to the executive user group receives an email from their Sisense admin including a link to the 3rd Quarter Western Region saved search. They click the link and are directed to the new strategic dashboard with the filter set for the 3rd Quarter Western Region applied to the available filters.  The viewer reviews the data and reviews the other available saved searches for the additional quarters that were provided by the admin. The viewer clicks on the 2nd Quarter Western Region and the filter set populates in the filter pane.  After reviewing the filter sets provided, the viewer adds regional subdivision filters based on the territories of their Western Region managers. The viewer creates the "West - Territory 1  (Q3)" saved search and shares it with their West - Territory 1 manager only and sends a notification to the manager. In addition, the viewer identifies issues with two specific teams and filters to these teams in the manager's territory. The manager filters to the two teams as well as the product's where issues were identified. The viewer saves the search as "{Manager Name} - Quality Assurance Focus" and sends a notification when sharing the search to the manager. The saved search allows the manager to quickly highlight focal points with his manager so that the manager can review the data the director sees prior to meeting and discussing the issues at hand.       ... 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

Users would like to be able to define the text sent in the email notification body. Each report sent via Report Manager could have a different text to explain the content of the report / the frequency / the purpose ... For now, it only possible to customize the email body at the server level ... View more

It would be helpful to choose where on a dashboard to add a new widget rather than it only being added to the bottom of the dashboard. ... View more

Ability to sort the items of a filter by a secondary item. Currently. for days of the week, for example, they will naturally be displayed in alphabetical order. Instead of "Mon, Tue, Wed, Thu, Fri, Sat, Sun". Sisense is only capable of displaying it as "Fri, Mon, Sat, Sun, Thu, Tue, Wed". ... View more

For some reason when editing a Pivot for example you can get 3 options for sorting on the "rows" - DESC, ASC, and No Sort  However when using the sort in the Pivot table itself - there is only DESC and ASC order. Could you please add the "No Sort" option to the widget too? ... View more

I think table and custom table usage should be added to the scope of usage analytics. I have large data sources that have been around for many years. Often dashboards are unused (which I can currently track with usage analytics) and can be deleted or archived. But the data that drives them is much harder to keep track of. I have no way of knowing which tables are used in dashboards and which ones could be removed. This is especially true for custom tables that eat up build time and might not be used at all. ... View more

Please add support of the First day of the week for the Live models. ... 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

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

Upon receiving the warning "Maximum number of series (50) exceeded", the warning does not reappear with a widget, dashboard, or page refresh. Instead, a filter change is required in order to trigger it again. IMO the warning should persist with refreshes and be visible every time due to the impact of the limitation being exceed - data is literally missing from the widget and the widget does not reflect the data set expected by the user.  To that end of being clear about the impact of having more series than the limitation allows, the warning would be best reworded to indicate that impact and avoid users making decisions on an uncontrolled subset of data. For example, "Results limited to maximum number of series (50)..." or "Data limited..." This limitation should also be documented in Sisense documentation, but is not currently. ... View more

Hi, Currently in the filters, we are unable to directly filter a comma separated list of entries. The options available are individually selecting the members, however that can get tedious if the list of entries we need to filter are large. For example, filter more than 100 entries. The other option is using the custom option in the filter. However, that too requires JAQL code which might be difficult for non technical users.  It can be useful to have the option to directly copy paste a comma separated list of entries in the filters instead of multiselecting or using the custom JAQL option.   ... View more

We have had several users complain that the way series selection for charts is not intuitive. Currently, when you have multiple series in a line chart and click on one in the legend, it gets disabled to highlight the others. The intent is to allow focus, but it's the wrong way around - most users expect that the item clicked should be selected and the others hidden. The current behaviour is quite painful if you want to see one series when there are several (you have to click on all the others). Is there a simple way to reverse the selection behaviour, or do we need to look at other options: wrap the control and handle it ourselves (possible?) build some drop-downs/UI to allow selection of whats shown some other neat UI work-around?? ... View more