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

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

To filter any data we need to add the filter on the right panel. Though this is possible only for a desinger and if a viewer wants to filter any other columns in the widget after the result set is displayed, they will need to download the table and filter in csv/excel. It will be really nice to be able to further filter the result set by viewer after the data is processed/displayed by having this option visible on every column header. Currently, clicking the column header only sorts the data, keeping a filter option on every column can allow the user to narrow down the results before downloading the file. Using this option, the viewers can filter any of their columns in table widget without having the need to download and analyze the results outside sisense. ... View more

We are OEM with several hundred client organizations, each of whom have their own set of our standard data models. The data sources are prefixed with a client code so that the same data model can be distinguished and secured between clients. Have two sets of the same data models with different data.  Have two users, each with access to only one of the two sets of data models. One user creates a dashboard that uses multiple data sources. The dashboard is export to .dash file and shared to the other user who imports it. The second user then needs to update the dashboard data sources to see the dashboard render with their data. Importing that dashboard into Windows and updating the data sources: 2DSDashImportWindows.mp4 Just update the data sources at the dashboard level. Importing that dashboard into Linux and updating the data sources: 2DSDashImportLinux.mp4 Update one data source at the dashboard level. Then update each widget in the dashboard to use that data source. Then update the other data source at the dashboard level. Then update each widget in the dashboard to use that data source. How many widgets in your dashboards 😉 ... View more

While downloading a large csv/excel file (over several hundreds mb file) from the widget, there would be a long delay of couple minutes before the browser indicates the file has been downloaded. During this time, the user has no indication if the request to download is in process or has failed. It would be good to have an indicator to show the download of the file is in progress, so user would not click the download multiple times thus causing multiple queries to hit the backend.   ... View more

In addition to not being able type in dates with the Calendar item in the date filter (I submitted that as a separate idea to be able to type in dates), the general date selecting user experience is quite cumbersome.  It's hard to write this out and much easier to show.  But the short story is that it is difficult to select the dates on the first try.  A pretty typical interaction with the calendar component goes something like this: Open the filter Select Calendar Pick the start date Perform however many clicks it takes to get to the date you need (sometimes this can take a few clicks if you are going back a few years/months) At this point you think you have selected the start date Now, move your cursor to go select the end date At this point, the start date loses your initial selection.  I think this happens 90% of the time Sometimes the issue is that the start date gets set to the new end date Sometimes it resets before you even get to the start date Sometimes it goes back "Select" like you never picked a date This behavior is quite frustrating.  I have experienced it quite a bit myself and customers have complained.  I hope there is something that can be done to improve it. ... View more

Current State: As of now Sisense supports adding of pulse alerts only for select chart types, like, Indicator, Area, Line, Bar and Column. Expected State: Sisense shall allow rest of the chart types as well to add pulse alerts. It is observed in other competitive products to be available for all the chart types. Customers like us (Blackline) have many use cases of tabular widgets and end users expect alert to be added to these widget types.  ... 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