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

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

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

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

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

It's great that in the formula editor one can add as much empty space as one likes to make the code as readable as possible... spaces, returns, blank lines, etc. Also great that fields in the formula editor can be renamed from what they are in the data browser to detail, for example, how a field is filtered. We can also hack that feature to add in a [Value]*0 as a comment. Still, revisiting big formulas is time consuming because of the lack of code comments. One can create an external repository that includes comments, but formulas cannot be copied and pasted from an external repository into the formula editor, making an external solution not much more helpful. So having a way of commenting in the formula editor, or a way to store formula code somewhere else that allows for commenting that also allows for easy update in Sisense when the code changes in the external repo.   ... 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

It would be great if Sisense would allow to sort a table/pivot by multiple values, combining ASC and/or DESC and indicating the sequence for sorting, e.g. by Field 1 ASC, then Field 2 DESC, etc. For instance, I am attaching an example with two values, so that I could sort based on % Compliance first and then by # Assignments, both in descending order. Additionally, it would be great to sort a table/pivot based on a field/value not displayed in the table/pivot. Currently, we need to use a script to hide that particular column. ... View more

While using the calendar date range in a filter, you should be able to type in the to and from date.  The old style filters allowed that option.  We recently switched to the "new" style (I say "new" because they are only new to us ... I think they have been available in the product for a long time).  In the new style you have to use your mouse to pick the date on a calendar, you can't type it in.   ... View more

Currently Embed SDK doesn't provide a function to perform the same function as clicking Restore my default filters button in dashboard filter. It would be great to add it in the future. ... 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

Please add support of the First day of the week for the Live models. ... 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

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