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

Currently you only provide a direct link to a dashboard.  Allow the ability to have the ID of the dashboard. That way customers embedding the dashboard into their main app can load it natively into their app instead of directing the user directly to the Sisense instance. ... 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

The in app Look and Feel UI theme editor is an improvement to the CSS editing of the past, but it has removed some capabilities that were possible in the past. Items that should be added to the theme editor Primary Button Outline color Cancel Button Outline color Primary button hover state text color Cancel button hover state text color ... View more

As the platform has users across the globe, the timezone chosen for reporting must get aligned with the logged-in user's locale. SiSense already displays the ElastiCube's last build time in the logged-in user's timezone. In similar lines, whenever a widgets reports intra-day transactions / volumes, an option to display the data in logged in user's timezone should be made available by default in the SiSense platform. ... View more

Similar to widow-orphan control of Paragraph page breaks in MS Word... it would be nice to have this in pivot tables too. That is, let's say the existing rows/subtotals in a pivot table take up 20 out of the "rows per page" value of 25.  If the next sub-section to display is going to take 3 rows, great, show that section.  But if the next sub-section is going to show 10 items, it means the subsection/subtotal will be split across two pages.  This is hard to remembe/digest/use when interacting with the dashboard.  With widow-orphan control, it would do a page break "early" before showing that next subsection of 10 items. ... View more

We have a use case where we need a Viewer role to have the ability to import and share dashboards. The problem is that those elements are set to canBeOverridden: false. Please change share and import to canBeOverridden: true for the roles API. ... View more

We have a client who really wants to leverage email preview (rather than or in addition attached PDF) to send important metrics to their leadership team.  However, most of their reports do not fully display because the preview only uses portrait mode. Request the ability to either specify portrait/landscape mode when setting up the schedule, or just naturally follow the format that best fits the dashboard. ... View more

To ensure security and compliance for HIPAA, we need to know when users export data. Specifically, we want to know how many rows were exported so we can check for malicious use.    ... View more

Hi all, Repost of my question in the community forum: Let's say I have a bar chart in my dashboard displaying number of customers over time with customer segments (small, regular, top) in the break by field. When I turn on 'widget affects dashboard filters' I noticed that the dashboard filters are not affected by whatever is in the break by field. I would like an option where I can filter the dashboard by both. From a user perspective it also makes sense. E.g., when a user clicks on the top segment in february 2022 then all other widgets in the dashboard show the values for top customers in february 2022. Kind regards, Kevin ... View more

My team was adding scripts to widgets to add attributes to the embedded widget and noticed an opportunity to expand what metadata we can use in the scripts. Currently, we're using the widget description (`desc` field) to set a testid attribute, but by default that description is viewable in the embedded widget.  I'd love the ability for designers to add key/value pairs to the Widget class metadata that are accessible in the widget script. widget.on('domready', function(w) { const { oid, customMetadata } = w; // customMetadata is the new (optional) property on a Widget const testId = customMetadata['testId']; // a key/value pair added by designer const selectorString = `[widgetid='${oid}']`; const widgetElement = $(selectorString); widgetElement[0].setAttribute('testid', testId); });   ... View more

Under an Admin Account and User Mgmt. it is not easily possible to sort the user role (ascending/decending) like it is with other columns.  License utilization is one thing, but being able to easily filter roles and reassign as needed would be a huge help ... 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

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Sisense doesn’t have an API to get data from the Sessions Table. This data is available in the UI only. We would like to be able to use this data in a custom application that we have built. We’d like to see an API that will allow us to get the Session Table details.   ... View more

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Custom queries are case sensitive by default. There are workarounds possible, but are just not productive. Every custom query requires something similar to the following: LEFT JOIN [MedStorageUsers] mu ON upper(mu.UserID) = upper(c.UpdatedBy) I want a global option in Sisense to automatically add tags that makes all custom queries case-insensitive ... View more

Our primary brand colour is red with our second colour a dark blue, but if I make that the main colour (as I would like), then my buttons become red and cancel buttons need to be another colour. It makes sense for the cancel buttons to be red and I understand the concept in making buttons the same as the primary colour, but in this instance we really want to be able to change that setting and have the buttons be blue so that the cancel buttons could still be red. If I make the primary colour our brand blue then the whole site looks black and white. Suggestion: allow the button colour to vary from the main colour. ... View more

Right now, if you're making significant changes to an existing cube, the only way to verify that you haven't broken something is to actually do a build. I'd like a Verify or Validate button, next to the Build button, that would do the initial steps of the build process and then stop.  For example, determine if the metadata in the table can actually be retrieved from the underlying data source.  Or checking datatype mismatches in existing joins.  And so on.  Just leave out the last step where you actually retrieve the full data set and then build the cube. This would save time during the development process. ... View more