Currently, if we export the pivot as an excel/csv, there is no indication of the date range it was run for in the output file. It will be really helpful to have control on the exported output in excel or csv, such that we can include the date range of the result or other filters applied in the output. ... View more

The number of source of frustration and confusion amongst our users, when building Dashboards, is conflicts/inconsistencies between Dashboard and Widget filters. I have separately suggested that Sisense introduce a visual indicator of widget-level filters and it sounds like that is planned for the future, which is great. Another related feature that a user suggested was a "reset all widget filters" button which would be a single place at the Dashboard level. If the user clicks it, it forces all Widget filters to (a) be deleted (or maybe disabled?), and (b) puts the widget filter settings back in-sync with the dashboard (meaning if the user has selectively toggled off Dashboard filter inheritance at the widget level, that will revert back to the defaults). This is a really quick and easy method to put users back to square one if they have painted themselves into a corner, so to speak. ... View more

Cube build alerts via webhook should receive which cube has triggered the alert. This is required especially when we configure a single alert for multiple cubes As of now, we are only receiving following info. {buildSuccess: false, name: Cloned sisense alerts, type: build} With this info, we do not understand which specific cube has failed. ... View more

This idea aims to help on-premises installations or live connections to better control load. The scenario: we have a big amount of users using the Report Manager plug-in, and we cannot limit the number of reports they can create or even the minimum periodicity for their schedules. Currently any user will be able to create a big number of reports, and those reports in a worst case scenario could be sent every hour. It could case a high usage of server resources. It is possible to setup the number of concurrent reports that will be processed, but depending on the number of reports it could cause bottlenecks and big deliver delays. The idea: adding some new 'admin' settings to Report Manager plug-in: - Maximum number of reports per user: defines the maximum number of reports a unique user can create. We could use 0 for unlimited (current behavior). - Maximum number of reports per user group: defines the maximum number of reports a user group can create. Same ideia as the above, but related to user groups. It could be a unique setting for any user group, or maybe a map with specific limits for each user group. - Minimum periodicity for scheduling: currently Report Manager offers the hours, days, week and months options. For instance, if this setting is set to days, then users will not be able to select hours when creating new schedules. Current existing schedules could be kept. ... View more

Current behavior of the Simply Ask feature doesn't support automatic saving of the modified NLQ model to the "*.dash" file. So you loose your development work after exporting the dashboard with already enabled and tuned "Simply Ask" to a "*.dash" file. After importing this dashboard back to Sisense the feature is automatically disabled. Also if a developer will enable it manually it starts running based on the "By Default" NLQ model. This forces to redo all the work on the model back again which is time consuming and not efficient. We expect Sisense to consider in the future the development work on making this more convenient for a BI engineer. If a "Simply Ask" feature will be automatically enabled on an imported dashboard with a corrected model, it would be beneficial for dashboard deploy automation and will reduce unneeded additional manual work on setting up this feature again and again for different working environments for the same dashboard. ... View more

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

Perspectives is a great addition to the application and making only certain parts of the model visible to those dashboards connected to that perspective is excellent.  Adding the ability to filter the perspective is something that is required for many of the use cases we have.  For example, we have a model that has All Tickets.  We have many dashboards that have a locking filter at the top to show only Open Tickets which doesn't look good from a user and design point of view.  Being able to create a Perspective and not only be able to refine the columns but also filter to (in this example) Open Tickets only would greatly add to the power and usability of this feature. ... 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

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

I would like to know which features of Sisense the users are using. Are they using Pulse? how much, in what ways? Which users have scheduled email reports (not the plugin)?  frequency, sending to self or others?  ... 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

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

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

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

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** We are hosted on Azure for Sisense. When looking at hosting Snowflake in AWS, it complicated out could architechture too much. We are looking for an option to continue to host using Azure, but also benefit from Snowflake. ... 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