Please add support of the First day of the week for the Live models. ... View more

When opening a support ticket, it's required that a large form be completed. Among these is the Sisense Account Type, Environment, and Version. We too frequently open a support ticket only to be provided with a response unrelated to the information provided in these fields (e.g. a Linux based recommendation after specifying the issue is occurring in a Windows environment and being asked for a version number after the information was already provided). Given the global distribution of Sisense support resources, it can already take a day before expecting a response, but for that response to then be unaware of the information provided in the ticket details causes delays, extra rounds of communication (especially when our support rep doesn't realize that the Sisense response is for the wrong version), and frustrates our support teams and the clients they in turn support. And we imagine the Sisense support reps don't love finding they sent irrelevant advice and don't like seeing our support reps' confusion when they aren't already aware of the information provided in the case opening form. We appreciate Sisense support reps and want to see them support us with as little friction as possible. Thanks. ... View more

WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL ... View more

We want to be able to disable jump to dashboard for certain rows in a pivot table and bars/pie-slices in various charts.  Currently we are only able to disable it completely. We would like to be able to be more specific on the disabling and only remove the jump to dashboard capabilities on the specific rows or bars.  ... View more

When the sisense user is deleted the email of this user is still in the recipients list for a report in the Report Manager. If the report Manager is configured to send the reports to external customers, the user who is no longer with the company will be receiving the reports with dashboard data as the reports for the external users are generated using the owner or an additional user. Thanks. ... View more

When we are building pivot tables, sometimes there is a need to sort things by the columns. If I want to show a pivot table with a Team Lead as the rows, Total Spend and Total Volume as the values, and Weeks as the the columns, I have no way to sort this to show the date in descending order and keep the table structure the way I want to see it. I think it would be helpful to have this option. ... View more

When a user makes an edit to a report, they can click Publish Changes so that report with those edits are live for users to see. Our customers would like to have an undo button so that the edits made in the last push is reverted and the version prior to publishing changes is now the current version. ... 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

Sisense does not currently offer the ability to easily freeze the top row of a pivot table, similar to what most spreadsheet applications offer. Prior community questions on this topic (such as https://community.sisense.com/t5/build-analytics/freezing-the-header-row-for-a-pivot-table/td-p/3022) advise a workaround by manually disabling the Auto Height feature for the pivot table widget, then reducing the height of the pivot table until a widget-level scroll bar appears.  This solution only works for a very specific use case, and losing the ability for the widget to dynamically resize when populated with different sizes of datasets and/or when applying dashboard-level filters makes it less tenable. For example, if a widget is manually resized so that the header is visible when scrolling for 50+ rows of data, the widget will stay the same height if a filter is applied that reduces the dataset to 15 rows. We'd like to see if there is a way to easily freeze the header row of a pivot table while preserving the ability for the widget to automatically resize based on the amount of data. Ideally this would be a checkbox or other easily accessible widget-level setting. ... View more

When using dependent filters and selecting new filter values this automatically resets all filter values already chosen.  Whilst this is desirable from a security perspective, not all models have security applied.  The proposition here is to have a toggle or similar that the designer/owner of the dashboard can use to turn this behavior on/off.  Thus the reset reasoning behind this can be maintained if required for that model or use case and the behavior can be turned off if non resetting is optimal for the use case needed. ... 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

Hi, I have issue with setting two date dimensions in dashboard. The goal I want to achieve is to have a history of records, which are also have it's own date dimension. You can download model and dashboard. I would like to have difference in growth ower selected period for defined dates. For example 2 days ago I sold a car for 1000, and yesterday the proce have changed to 1500. The sale date is for today. So the growth over 2 days is 1500, and for 1 day 500. Additionally i would like to compare those values to previous year, and go back with both date dimensions. Tricky part is also, that if there is not sale for this year, PastYear() wont count prior year. I tried to play around with filtered measure plugin, however it doesn't give me exactly what i want. Do you have any suggestions how can I approach such data and 2 date dimensions? Thanks 🙂 ... View more

When I sort cubes in descending order and then click into a cube and come back to the list view I lose sorting. This can be annoying/frustrating. Can you make it so that my sorting remains until I change it? ... View more

Currently, dynamicElastiCube supports multi-model dashboards by indicating in the config at a widget level which data source to point to. However, there is no setting to do the same for dashboard filters. Thus, all dashboard filters will point to the "primary" elasticube when routing. This breaks any filter associated with models other than the primary one. ... View more

Custom Code is currently disabled in a multi-tenant environment, which is an odd thing to disable as it is among the many features that make Sisense so great because of the ability to manipulate the data within Sisense and part of the Tranform stage of ETL processes.  I am a Tenant Admin in my multi-tenant environment and I can click on Custom Code but I am not able to access the jupyter notebook environment. This creates a lot of confusion for clients who have multi-tenant environments and also takes a feature that the other clients have in single-tenant environments.  Sisense should seriously consider making this a permanent feature in all environments because it is so useful.  ... View more

The v1 Excel exporter included functionality that would export Pivot Table widgets to an XLSX file that was aggregated just like what users see inside of Sisense in their browser. We are now using the v2 Excel exporter and it no longer has this functionality, apparently by design. I think the v2 Excel exporter should also have aggregation functionality so that the XLSX export for Pivot Tables is just like what users were seeing with the v1 exporter. We have thousands of users who have been using the v1 Exporter and are expecting this behavior. ... View more

There needs to be a way to deactivate user accounts rather than completing removing. We have users that will no longer have access to the system, but could come back later (for example, trail users). The workarounds are currently: reassigning security groups (means those users are still taking up licenses) writing our own user admin functionality (only makes sense if we are integrating users to another platform) Adding a 'Status' or 'Disabled' flag to the user account would accomplish this. ... View more

It appears that once you've created a cube or live data set, you can't rename it. You can duplicate it, but I'd really like to rename some of our models without any of the associated dashboards breaking. ... 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