When editing a cube or live data source, I'd like to be able to more quickly add another table.  Right now, you click on the  +DATA button at the top, and get presented with all the historical connections, etc. Instead, what if you add an "Add Table" button inside the Data Sources panel?: That is, under the triple dots in red, have a new option to quickly reuse that connection and add another table. Then you'd avoid the proliferation of connections, also (the yellow connection list, in my example). ... View more

When generating the WAT token, we need to pass the Sisense user ID in the 'sub' parameter. To obtain the user ID, we must repeatedly call the Sisense APIs, which can be inefficient. It would be beneficial if we could directly include the Sisense username or email in the 'sub' parameter, thereby avoiding unnecessary API calls to retrieve the Sisense user ID. Reference Document - https://docs.sisense.com/main/SisenseLinux/using-web-access-token.htm#StructuredTokensByValue ... View more

The Pivot table Excel download behaviour was recently changed. Previously, merged cells from the pivot table on the dashboard view would persist in a downloaded Excel file. Now, rows are not merged and are simply duplicated (as with the csv download). While there are some upsides to this, this is a change our users and customers have reacted negatively to, asking us to revert the change, which of course we are unable to do. We would like the option back for a download which maintains pivot table cell merging, replicating the way these appear in the dashboard.  ... 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

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

Looking for a way to change the logo based on their corresponding theme. We can create themes for the different companies but there is no option for logo in the Theme and would like to capability to extend the white labeling past just 1 logo ... 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

The idea of this is so you could show the elasticube data on the primary axis, and then potentially low latency data on a secondary axis - allowing easy comparison of live vs historical data ... 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

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

Currently, whenever a user starts a build in a cube, either everything is updated or only the changes that were made. It would be incredibly helpful to have the cube refresh only certain tables as indicated by the end user. ... 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** The Data Designer, when modeling an Elasticube or Live model isn’t able to define the default aggregation method. When adding a measure to a widget, an aggregation method is automatically applied. The Dashboard Designer can choose the aggregation method via a menu, but a regular click will always choose a predetermined system-wide defauilt (distinct count or sum). In some cases, the aggregation applied is not relevant and could lead to invalid results. I would like to see a feature that allows a Data Designer, when designing the data model, to define the default aggregation for a column. A Data Designer has the knowledge of the data model and what aggregation is best used for it. This ability would assist Dashboard Designers in correctly using the model. ... View more

When creating a widget in SimplyAsk, We would like to see the download option extended to offer exporting to excel/CSV if the table viz is the best option. Some viewers might not be able to pin it to the dashboard but still want to extract the insights.  ... 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

When you export a datamodel to a .smodel file, the file includes connection information (server name, password, etc.). I would like an option to exclude that information when I click export. The export dialog already offers check boxes for Data Security, Scope Configuration, etc.; this feature could be just another one that says "Connection Information". Ideally, I'd like it to exclude the connection information by default, so users are forced to explicitly ask to include it, which will remind them to consider the file as sensitive. But I understand if you don't want to change default behaviour that other users are used to. When you import a model that has had this information removed, the import should let you to enter new connection information, or leave it as placeholders like Server=0.0.0.0 and password=Password so you can enter the information after importing. Sisense GIT already removes this information; this feature could work in a similar way. You could even deliberately make GIT's "non-tracked entities" all appear on the list of export options. GIT per this page: https://docs.sisense.com/main/SisenseLinux/asset-translation-and-management.htm?tocpath=Git%20Integration%7C_____3#Non-trac ... 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

Hi, Our CSMs/Marketing teams using downloaded PDFs as additional information to our customers. A need was raised to make the PDF generated more company branded, including the company logo (which includes in the platform).  It will be very valuable feature for a lot of internal users in the company.  ... View more