Currently , If we have to create a schedule using report manager, we need to save a copy of the dashboard with the filters applied and then schedule that particular saved copy. Thus, if for a single report i want to create multiple schedules, i have to create a separate dashboard copy and point the schedule to that copy. It will be much better if we can create the schedule directly on the dashboard and add filters specific to that schedule. The only option i see is to overwrite the dashboard filters using the 'Apply custom filters' option. However, this brings up a JAQL script which the end user may not be familiar with.  Thus, to enhance report manager, it will be better to add the below options: 1) Allow user to create a schedule in report manager from the dashboards page, instead of going to the report manager plugin. 2)Add some form of UI when adding custom filters instead of displaying JAQL code, so end user would be able to easily overwrite the filters in the same dashboard by creating multiple schedules instead of multiple dashboards.   Note: It is possible through a third party plugin, but would be better to incorporate this in the existing report manager plugin. ... View more

Current Functionality: The fiscal start year for an Elasticube can be set independently. Ex. in the elasticube fiscal year start is set as October. When a dashboard is connected to the Elasticube, the dates correspond to the Fiscal Year (FY) starting October. However, perspectives linked to this Elasticube default to a January fiscal year start. And there is no way to change the fiscal start year at the perspective level. Desired Functionality: When a dashboard is connected to the perspective, the dates should ideally correspond to the Fiscal Year (FY) in alignment with the parent Elasticube's settings or there should be an option to configure the fiscal start year exclusively for the perspective. Importance: This enhancement is significant as perspectives are being explored to enhance data and analytics implementations using Sisense.    ... View more

It would very helpful to be able to see the columns of a table in the Table Query section of the MySQL query build. Currently it just list the tables and you have to open another table then preview the table and scroll sideways to see the available column. You could create this in a tree view like SQL Sever does. This would help query writers by being able to see what columns belong to the tables, I included what SQL Server does for reference.   ... View more

While using the date picker for the column definition in the report if the column is defined at a years level Date picker still shows all other options for date formatting including quarters, days, time e.t.c, but if you switch to those they have no effect at all, since it goes off of column definition. Maybe those options should be greyed out, besides the one that can format data at the same level as defined in the column, to make it less confusing for the users, or as an alternative, if a different level of formatting is selected, to automatically switch column to that level of definition. ... View more

We have reports/dashboards based on a large underlying table. Thus, when a user tries to run a dashboard for a long date range which would result in many rows being processed, the dashboard may take time to load. It will be helpful, if there is a way to get the size of result set that will be executed using the query plan. Using that estimated size, we can compare the size to a threshold size defined for the dashboard and if the estimated size is greater than the threshold, the user can get a popup message which will indicate the result size being too large will impact the dashboard load time. Thus, in this case, the user can alter the filters to reduce the result size if it wants the results sooner or else will be expecting the results to take time due to its size. ... View more

Request: Provide a standard way for supporting multi-currency support. Use Case: Enable end users to create widget and dashboards where they can switch between multiple currencies. Background: There are various posts on how to implement multi-currency by adding an exchange rate dimension and using a formula similar to Local Amount = (Amount Field) * (Exchange Rate) and using a filter to select the desired currency (E.g. USD, EUR, GBP). This process works well when you have dashboard designers, but it doesn't work well if you want end users to create their own reports.  If they do things wrong the Amount may be multiplied by the number of currencies supported. They are required to enter a formula instead of simply selecting a field to report. Recommended Solution: Add ability to add Formula fields to the data Model.  The data designer would create a standard field with the formula.  The formula would be evaluated within the dashboard not during cube build.  Note: there are probably other uses cases for data model defined Formulas that are evaluated within the dashboard. Add ability for automatically adding the Currency filter when the data source is used. ... View more

Sisense maps are running on Mapbox. Mapbox supports localisation, i.e. showing the map objects like countries, cities etc in a chosen language, see https://docs.mapbox.com/help/troubleshooting/change-language/. I would be great if Sisense could support translation of maps by e.g. giving the user's preferred language as localisation parameter to Mapbox. ... View more

We have a use case where a report schedule is supposed to run daily/weekly only during certain months of the year(seasonal reports). This could be done using the time frame section in report manager, however, at the end of the season, we will need to manually update each of the schedule's start and end date, which may not be feasible when there are over 100s of schedules as such. It will be really helpful to be have this ability in the schedules, so schedules can run only certain months in the years. ... View more

The UI limits the number of recently used drill-in fields to 5. I've attempted to write custom JavaScript to add additional entries to widget.metadata.drillHistory, and verified they are added to the array successfully, however the UI will only show 5 drill-in values. This is important because our customers need to be able to "slice and dice" data visually and the best way to do that on a single chart is by using drill-ins. We do not want customers to have to "Choose another" because nearly all of these customers are viewers and do not have or need extensive knowledge of the data model. Having an option to increase this, either as a dashboard JavaScript override, or as a feature in the configuration of the product itself would be very beneficial. ... View more

Current state - You can only use color conditional formatting on numerics in the value section of a pivot table.  But it would be nice if you could also apply color formatting on text.   An example of this would be green on the value 'Confident', orange on the word 'At Risk' and red on the word 'Not Possible'. This text would be values existing in our database, not something created within Sisense.  ... View more

Currently the way the Sisense creates its query for dashboards, is it creates a common table expression for each entity created in the data model. Then applies the date filter after the join between the CTE.  During this process, it looks like its scanning the entire table of the CTE, which can be problematic if the underlying table used in the CTE is really large.  It will be better if the filter for dates can be applied within the CTE for such large tables, thus avoiding large table scans and help load the report faster. Is there a way this can be achieved by altering the design of the data model? or are there any plugins to support it? ... 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

When using Starred Filters, end uses can create their own filter and save the selection for repeat use. However, any Starred Filter created will be visible to all users regardless of their Group or Parameter assignment. This is because these items are stored in the Data Browser as additional elements linked only to the data source and not to a user or group. As a result, this causes confusion, lack of control where one end users Starred Filters can be removed by another and concerns about data security. Appreciate utilising multitenancy would be a solution, however, this is not possible in all circumstances and requires a significant amount of additional administration.  I am recommending a functionality change to control / limit the visibility of Starred Filters to the User or Group that created them.  ... View more

Allow users to customize and set their preferred date format across the entire application interface. This feature would enable the seamless adjustment of date displays to match regional or personal preferences (e.g., MM/DD/YYYY, DD/MM/YYYY, YYYY/MM/DD), ensuring a consistent and user-friendly experience. Admin will have the ability to select their desired format once, and the change will be reflected globally across dashboards, tables, and all date-related elements of the UI. ... View more

Our users often ask about concatenating strings contained in two separate columns as a calculated column in pivot tables. Although this is possible at the data model layer, it is not possible at the dashboard layer. We do not expose data model design and administration to our end users. Would be very helpful for Sisense to introduce this functionality. ... View more

Suggestion for improving subscribed dashboards: Include the date/time of the last cube build in subscribed dashboard emails.  Currently, we see the date/time per the settings configured in the subscription. We'd like to also see the date/time that shows when the data was pulled, or the "as-of". If there is a discrepancy in data, or if/when we need to trace back and review platform data changes, or if changes are made after the subscribed reports that may be important to call out to shared dashboard subscription recipients.  Thank you! ... View more

Currently, when we select the option to highlight in a widget data is, nevertheless, usually sliced in other widgets using different categories. Imagine we have three bar charts and a table, all of which are marked as HIGHLIGHT. Each widget and table contains a different category, this is the relevant part. I would like to be able to select a category in one of the widgets and be able to see all elements in the other widgets, but just highlighted. Currently, since these are different categories than the one selected, they are sliced. In attached image, I am selecting a category in the second widget but all the other widgets display sliced data, despite having selected highlight.   ... View more

We create filters on certain records that have long names, sometimes with similar names.  The current width of the filter panel cuts off these record names and makes it difficult to find the correct record(s) to select. We suggest either making the filter panel size-able, or possibly at least wrapping the name. ... 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