The page controls to change the pages are currently within the widget and its functionality is limited: Thus, if the number of rows to be displayed are increased to 50 or so, the widget window would get expanded and user will have to scroll to the bottom of the dashboard to see the page controls or change the widget page.  This can be avoided by placing the page controls at the bottom of the widget window and not limiting it to the size of rows. So the widget window size stays fixed and the user can scroll through the data within the table widget. This also helps view the dashboard in the page  without having the need to scroll down at the bottom of the dashboard. Additionally, also allow the viewer to increase the number of rows to be viewed in the widget. Example, a user should be able to increase the number of rows for a table widget to fixed numbers as 50 or 100. ... View more

For the pods that sisense deploys into the kubernets cluster (bld and qry pods) being able to customize these specs would be helpful to get true node isolation and for log shipping. Currently we can set the Limits and Requests for these pods. It would be nice if there were a configuration setting that would allow us to add a toleration to the spec so our cluster can use taints. Also adding custom annotations to these pods would allow us to ship the logs to our log management system giving us greater insight and monitoring.  ... View more

It is currently possible to add a second axis, but we would like to expand this capability to have more axes on a chart or line chart with Compose SDK. Data visualizations are becoming more advanced and to match our competitors, we would like to have this capability to build a chart where users can select and display multiple measures on one chart. For our future dashboard, we plan to have a longer list of KPI measures that users can select from to ensure a customizable and interactive experience. ... View more

Hi all, Can there please be a way to export and import the "Look and Feel" themes in Sisense? At the moment, I've got a dev and prod instances for Sisense and 50+ clients who we aim to have custom themes based on their company branding and colour schemes. After making and testing one out in Dev, I'd love to be able to just copy a theme over from Dev to Prod when promoting a dashboard up instead of the current process of going through each individual settings and copying each colour one by one. Kind regards, Shams     ... View more

Currently, the Area Map widget only offers two map types: World and USA. This becomes problematic if your data is limited to a specific country (Indonesia, in my case), and you only want to display that country on the map. I've managed to filter for Indonesia using the following code: ...res.geoJson.features.filter(feature => feature.properties.name === 'Indonesia'), However, this approach leads to another issue: when the dashboard loads, the Indonesian area is too small, and I have to manually zoom in. I would greatly appreciate any code or method to set the widget to automatically zoom into the Indonesian region when displayed on the dashboard. ... View more

Idea: Allow developers to build/test add-ons in a local environment rather than requiring a live environment. Note that this would be for the purpose of creating custom add-ons for additional functionality that would require testing on the "out of the box" Sisense UI. Background/Context: In most development workflows it is common practice to work on your code locally on your machine and deploy to a local server aka "localhost" to test/view your work in the browser. An example of this is building and deploying a local React.js app to your browser. As you make changes to the code it will recompile locally and update what you see on your localhost. If you're using Sisense out of the box however, to test/view any changes to an add-on developers are forced to upload the files in some way to a live Sisense Environment. This not only limits the innovation of add-ons to developers with an active license and live environment, it makes it painfully inefficient to develop customizations on top of the Sisense application. I understand there are likely some business concerns with allowing the use of the product locally but I'd argue that there are ways to prevent that, such as enforcing some default sample data etc., but in such a way that would give developers a "local playground" to develop/innovate on. ... View more

In report manager, when trying to add recipients for email, we receive sisense user email id suggestions based on keyword entered. This can be confusing to users, as our end users send emails to external recipients(non sisense) and that email id suggestion is sisense internal user email. It will be really helpful if we can have a functionality to disable these email id suggestions from popping up in report manager, and avoid confusion to users.   ... View more

In dashboard filters we currently cannot add custom tool tip to filters. While using the dashboard, it will be helpful to add some tool tip description to the filter which may pop up by hovering around it or through some information icon. For example, if a user needs to use a custom filter, the JAQL syntax may not be intuitive. Using some tool tip, will help a user understand how to use the filter in a JAQL format. ... View more

NOTE: This is based on a post I made in the "Help & How To" forum. It was recommended to me to make a post here, in the Product Feedback forum, about it. There should be a way for Sisense to display the currently-selected filter values directly on the dashboard. I know that users can see this by expanding the right-hand sidebar to see the Dashboard Filters, and it's also a display option when you export to PDF. However, these aren't always obvious or available to the intended audience for the dashboard. For example, if I have a dashboard that's setup with a dashboard-level filter for "Work Group", it would be nice if I could display - directly on the dashboard itself - what work group is currently being filtered down to. Also, some of the values can be unclear, especially for date filters that use colloquial language such as "This Year" or "Last Quarter". There should be some way of displaying the exact date ranges that are being filtered for. For example, if today is November 13th 2024, then the "Last Quarter" filter value would mean dates from July 1st 2024 through September 30th 2024. But after the new year, if I were to check the dashboard again on January 6th 2025, then the date range would instead be from October 1st 2024 through December 31st 2024. Currently, in both cases, it'll just still how as "Last Quarter" and it's up to the user to figure out what that means (which can be difficult if they're looking at a static printout from some unknown time in the past). Other time periods can also be ambiguous or prone to misunderstanding. For instance, it's common to see people assume "Last Week" means a rolling time period covering the last 7 days, rather than the prior calendar week. Or assuming "Last 2 months" means the same as "this and last month", rather than the prior two calendar months not including the current month.  ... View more

When we send more than one Combined Excel Report while using a dashboard having different filters on it. Names of those combined Excel sheet we get from them is same as they were using same dashboard for creating a report, which is difficult to identify when downloaded simultaneously. Can we base the name of excel sheet on Report Name itself rather than dashboard name as it will be more convenient. Thanks, Animesh Gupta ... 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

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

Hello, In a multitenancy environment, it would be useful to be able to define an email notifications sender per tenant. ie : Tenant "Tenant A" : mail sender is "Sisense - A" Tenant "Tenant B" : mail sender is "Sisense - B" For now, email setup is only available from the default tenant, therefore unique accros all tenants. Thank you. Franck ... View more

I use pulse alerts to alert my clients when there is data on Sisense that needs their attention. The Pulse alert emails are accompanied by a big yellow 'Open Pulse' button. This button is the obvious thing to click on, but unhelpfully, it leads to the 'Pulses' tab of Sisense, not the actual dashboard. As a viewer, I want to jump straight to the dashboard, not be confused but this 'Pulses' tab which I most likely will not have seen before nor used. An option to have the button instead open the dashboard directly would be much better and make it much easier to engage customers with the Sisense platform.   I know there is a link to the dashboard on the pulse itself, but going via this screen this is inconvenient at best and confusing at worst. ... 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

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

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

System emails like shared dashboards or report manager include links where the URL resolves to the Sisense instance. For white labeling / embedded products this doesn't work. If we had access to more variables when customizing templates we would have greater flexibility in designing workflows. Specifically if we had access to the <id> of the dashboard and instance & group level parameters this would make the messages far more customizable and useful in a variety of scenarios. Some of the other metadata as variables would also be very helpful and make emails more valuable. ... View more

It looks like the sorting on compose SDK charts is very limited.  You cannot pass a predicate (callback function) to define your own sorting, you can only specify ascending or descending. So, if that's the case, anytime we need to be able to sort a column by another column, we'll have to use the queryService and sort it ourselves. ... View more