Create a pivot widget of RSUM( [Total Quantity] ) over time (rows) and break by (columns) age range. Scanning down each column, over rows, the numbers only increase. Now change it to a line widget. The break by defaults from an RSUM within columns in the pivot to an RSUM within rows in the line chart. This is the same as not having an RSUM and doing a stacked area. Our clients expect the line chart the results from changing the pivot to a line chart, to reflect the same output as the source pivot. As it stands now, they are surprised to see negative curvature in their RSUM, think something is broken, and open a support ticket. The default behavior should be to render Break by Columns instead of Rows. As an aside, I'm having trouble coming up with, and would be interested in hearing, use cases for charts with break by set to rows.  ... View more

The content/formatting/text contained in the various Sisense-generated/automated emails is currently static. I went through a long dialog with support and determined that  it's not customizable by customers. I would like it if we could modify these emails, and I'd especially like to have access to dynamic variables that we can insert in the email body (or subject). User's first name or last name were specific for my use case, but having access to a variety of variable could be helpful. ... 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

There are many scenarios where a model contains data for many distinct groups, such as customers, and you want viewers to only have access to the data that pertains to their specific customer. This is easily implemented with row level security, when there is a data column that uniquely identifies each customer. But what if you have a requirement that certain types of viewers should see all columns of data per row, while others should not have access to certain columns? Here is an approach that can be implemented right out of the box in Sisense. The one prerequisite is that any table that contains sensitive data must have a column that uniquely identifies every row, i.e. a primary key column. For every table that contains sensitive data in certain columns, create a new table that contains the original table's primary key column, a binary "switch" column with a name like [Access Allowed] and a column for each of the sensitive columns. Remove the sensitive columns from the original table. Modify the import query to load only the non-sensitive columns in the original table. Modify the import query to load the new table with the primary key and sensitive columns of the original table twice, once with [Access Allowed] set to 1 and the second time with 0 and blank (or null) for all the sensitive columns. Associate the new table to the original table by primary key column Create a dimension table for secure access with the column [Access Allowed]. One row with value 0, one row with value 1. Associate the dimension table with the sensitive data table by the [Access Allowed] column. Set up a data security rule on this column, assigning the secure user group to value 1 and the general group to value 0 If there is a hierarchy greater than two levels of column-level data security, this model can be extended to create additional one-to-one related tables to the original table. ... View more

There are some dashboards where we don't want people messing with the filters.  Or where filters aren't needed to be changed, and we want the maximum "real estate" available for the body of the dashboard. I know you can hide the left- and right-hand panes with script, but this really should be an option exposed in the dashboard designer UI, as a setting for that dashboard. Example: Filter Pane:  Show [default]; Collapsed [but user can expand]; Hidden [user can't expand it]   ... View more

When creating a new table in an Elasticube, the area to write code into takes up a fraction of the screen space. Please make the pop-up to write code for tables stretch across the whole screen so users can see more lines of code at once. Or make the pop-up window adjustable so we can move it to be as big as we like.  ... View more

We get requests to add full charts to a Pulse.  The option doesn't currently exist in the dropdown. ... View more

Various features in Sisense can be whitelabelled. However, as well as the website, email notifications are another area of Sisense that customers will interact with. Email text configuration can be controlled via the 'email-templates.js' file, but there is not currently a way to whitelabel this text. I would like the option to change this text a deliver different messages for tenants. This would be useful for things like platform invitations in particular, to reassure users that an invitation from a 'Sisense' platform they may be unfamiliar with, is in fact associated with their company. ... View more

Sisense has some powerful whitelabelling features, but a key 'weak point' here is the URL itself. Currently, any Tenant has to be after the URL, e.g. for a company 'newcompany' at our company (Shepper), the URL would be shepper.sisense.com/newcompany. If we are delivering a whitelabelled solution for 'newcompany', where they want to whitelabel with newcompany assets only, there is no way to whitelabel the URL itself. I would like to keep the 'Shepper' text for most of our customers, but having an option to have an alternative URL for a tenant, such as newcompany.sisense.com (or even something that obscures our company's name a little, like shp.sisense.com/newcompany), would be the last piece of this whitelabelling puzzle. ... 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

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 embed and white label Sisense and our premium customers have the ability to author new dashboards with the formulas and attributes we provide. Our users want the ability to create new attributes, comparable to creating a new formulas. Examples: new "Northeast Location" attribute = existing location attribute that we provide where sites = A, B, C new "Shutdown 2023" = existing date field that we provide where date range between X and Y Concatenation of multiple fields to form a new attributes, comparable to Excel new "Is True" type attributes = existing attributes we expose if value(s) = ... Customers want the ability to create their own custom attribute, have then be added to the default values list, in their own "custom" section, where they can search and reuse their own creations. We are a multi-tenant solution provider so tenancy of these custom creation must stay "in tenant" and must do so with us implementing the multi-tenancy feature of Sisense (as we are already deployed and this is not yet robust enough for us to utilize) ... View more

A nice feature in Microsoft SQL Server is the ability to see multiple data sets from queries in stacked windows. Currently only one query can be executed at a time and only display that one query's data set. It would be nice to be able to compare data by having multiple data sets appear at the bottom. Currently I have to open multiple browser windows to compare values and it can get a bit busy. It would be nice to compare 2 or more queries in the same window. Select * from table 1 where id = 123 Select * from table 1 where id = 456 data set for id = 123 data set for id = 456 ... View more

Please enable the possibility of selecting a default CSI (storage class interface)  from a set of existing CSIs so that it may be used as default Sisense persistent storage option. This is is a necessary feature for persistence of storage in cases such as autonomous cluster scaling or rebalancing, as well as disaster recovery.   ... View more

A user would like to remove the title from the secondary indicator. Unchecking the Title box works for only the primary value. They would like the same functionality for the secondary. ... View more

We disabled the new Simply Ask option in the Sisense configuration but it's still showing as a disabled option when you click a dashboard's context menu. We submitted this as a defect but were told that it's "by design". It's by design to show an option that's been disabled? We don't want users to request the option be turned on, as the hover text suggests. ... View more

Would you consider allowing the retrieval of files from the nodes with the file management so that end-users can retrieve logs with having ssh access. ... View more

As of L2023.3, in Sisense’s Helm Charts , “Tolerations” are supported by the micro-services. It prevents end-users from configuring “Taints” on the node that they want to dedicate to Sisense. Since no “Taints” are configured, so all nodes can become eligible to host Sisenses’s pods. They experienced that scenario when pods from some other application services were scheduled on a Sisense node. Would you please consider allowing the pods to be protected not only with  “Toleration” but also with “Taints”. The justification for this is that, even though it is mentioned in prerequisites documents that Sisense should be installed on dedicated servers, there is a non-negligible factor from the customers perspective that is the overhead administrative costs, especially for customers who must already manage numerous clusters for several applications, multiple environments, and redundancy.   ... View more

There are cases where the Sisense queries have to read from views. Would you consider allowing to issue queries like “ALTER database.materializedView REBUILD”  instead of only allowing select commands, in this case this would allow to refresh data that would be selected by the jdbc connector. ... View more