We have a custom webhook mechanism to alert us for cube build failures. We created a single alert selecting all our cubes and adding the webhook link Given build alerts are owned only by a single person.  Ownership transfer of these is helpful when people move out of the team and new person comes in, If not,the alerts created for team will need to be re-created. Also, every time we want to add a new cube to the build alert, the owner of the common build alert should be available else we cannot add alert or will be forced to create a build alert for the absence period of the owner ... View more

I recently posted a query on sisense forum to increase the offset size of a pie in a piechart. I got a response how it can be done at a widget level, but there is no feature in sisense to apply this change at global level for all pie charts in every dashboard. In fact, there should be a global space where any change for any widget could be applied to all such widgets in every dashboard. ... 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

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

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

We are a multi-tenant software provider and we embed and white label Sisense.  In our setup, we have 2 models.  Model 1 is used by Engineering to create our pre-built dashboards, where we share these with specific groups we've set up so that all of our customers see our pre-built "out of the box" dashboards The second model is what we expose to our Premium users so that they can create their own custom dashboards.   There are times when our customers will create a new, custom dashboard with the second model.  These users sometimes share their dashboard very broadly.  When this happens, there are certain users that wish to remove themselves from the share.  Perhaps they don't have row-level security to see anything.  Perhaps they have changed roles or simply do not use that dashboard. Note that we do not want to allow customers to remove themselves from our pre-built shared dashboards, as this could cause support confusion as to why our analytics solution is enabled but a user doesn't see "all of the dashboards".   With the above noted, we would like a configurable means to show/hide a "leave shared dashboard" dashboard option, based on the model with which a dashboard is associated.  This will ensure that users cannot remove themselves from our pre-built dashboards (we would hide on our model) yet allow them to remove themselves from custom dashboards that were shared with them (we would show on model 2 for self-authoring) When a user leaves a shared dashboard, there should also be configuration options to alert the owner of the dashboard via email.  This email should be capable of white labeling.  It should include dashboard name, who left, and when.  Should there be links to the dashboard in the email, there must be a way to disable hyperlinks in the email. ... View more

In the left-hand sidebar where the list of Dashboards is shown, it would be nice if there was a visual indicator of whether a Dashboard that you own is being shared with anyone else. Currently, the only way to determine this is to click the kebab icon (⋮) next to the dashboard name and see if it says "Republish" (indicating the dashboard is currently being shared) or "Share" (indicating the dashboard is not currently being shared with anyone). However, if you are the owner of MANY dashboards, some of which are shared and some of which are not, then it can be very tedious to check this one-by-one. If you hover over a dashboard in the list, a pop-up will display with additional information, one of which is a "Last Published" date/time. However, this doesn't really help. First, it only appears on mouseover, so it doesn't solve the problem of this information being tedious to check/verify (since you still have to check each dashboard one-by-one). Second, the "Last Published" displays if the dashboard has EVER been shared, even if it's not currently being shared with anybody. For example, if I shared a dashboard with Bob, but then later removed him from the share list, then the dashboard is only visible to me and no one else, but the pop-up will still show the last time I published it to Bob (even though he can't see it anymore). There's also a visual indicator, to the left of the dashboards, in the form of an icon that changes depending on the status of the dashboard in question. Unfortunately, this icon only shows the ownership status of the dashboard, not it's share status. That is: it helps you identify at-a-glance (A) which dashboards in a list are ones you own, vs (B) dashboards that someone else owns and has shared with you. However, for the dashboards that fall into (A), there's no indicator as to whether you've shared it or if they are only visible to you.  Perhaps a different icon could be used to indicate each state. Another nice-to-have: for dashboards that fall into (B), i.e. dashboards that someone else owns and has shared with you, perhaps there could be different icons depending on the way it was shared with you. That is: whether the person shared it with you specifically vs shared it with a group that you're part of. Essentially, the icon should indicate all the possible states that a dashboard can be in: Dashboards you own that are not shared with anybody (i.e. only you can see it) Dashboards you own that have been shared with others Dashboards you do NOT own that have been shared with you Dashboards shared with you specifically Dashboards shared with a group you're in ... View more

We create a basic set of pre-built dashboards that we publish, where business users can view but not modify.  We also have two-tiers of analytics offering for business users (standard and premium).  On our common, pre-built dashboards, which are available to both standard and premium, we would like the ability to expose Simply Ask to only those users of premium (hiding it from those who are standard).   While this may be achievable via a 2-model, 2-dashbaord set approach, we desire to manage a single set of dashbaords and model to simplify deployment overhead and maintenance. ... 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

we have "label" field that have multiple values per entity and would like to be able to use the same field for both column and row in the pivot table. We will use different filter on column vs row so different values will be shown ... View more

To recreate: Go into any dashboard Click PDF at the top The pop-up screen looks like this The circled Paper Size A4 is the issue. ... View more

It would be better to have more control options over exactly when the email report for a dashboard is triggered out to users. Currently we use the option "Every Elasticube update. No more than 1 emails per day" but that has issues: 1) We would only like the email to send if the Elasticube update is successful, rather than every update (including build failures). Otherwise we send a report out with missing data. 2) The rule of "No more than 1 emails per day" doesn't seem to be working properly. Meaning if we refresh the Elasticube more than once per day, users are receiving duplicate reports. ... View more

It would be nice to allow a Widget to be viewed in full-screen when embed=true. If it could just fill to the size of the iframe that would be better than what it currently. ... View more

Currently Notebooks provide a powerful opportunity to access and visualize data utilizing SQL and to add these to fusion dashboards.  Fusion's primary analytics environment allows for powerful dashboard-wide filters.   Currently dashboard filters do not apply to charts or tables which are created through notebooks even if the notebook is pointed to the exact same data table and column as other dashboard widgets.   Please develop the ability for dashboard filters to filter both fusion dashboard widgets and also notebook-based widgets.   ... View more

Hello, It is not possible to rename a cube, but it is possible de copy it. If we then move the existing dashoards to the copied cube, we have workaround to rename the cube. But with Perspective it is not possible to rename nor to copy. => It would be useful to be able to copy (duplicate) a perspective. Thank you ! Franck ... View more

Some of our customers are being forced to upgrade Mongo, and we need to upgrade our drivers in order to match. On 2023.7 we are using driver version 1.3.11 which is not compatible with MongoDB 4.2+ and our customers mentioned they are being forced to go to MongoDB version 5 or 6. ... View more