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

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

Unsure if it has to do with the numerous columns that we have in this table specifically but there is no drag scrollbar to be able to see beyond the first 6 columns. It would be nice to enable scrolling despite numerous columns so that users do not have to manually download the report.  ... 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

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

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

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

Idea: usage analytics reports can tell what reports use a certain field? Filter by a certain field in the usage analytics report and you will see all dashboards using that field.  It would also be beneficial to track table usage in dashboards too.  Use Case: region will be renamed to region_usa in our sql query and this could potentially break dashboards. to be proactive, i would like to know what dashboards are currently using the field 'region' so that I can redirect them to the correct field, 'region_usa' once the sisense schema & sql has been updated. ... 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

As an admin, have an option at the top of a dashboard to be able to view it as another specific user.  For example, if user John Smith is set under the data security on a cube to only have access to rows for a certain region, the ability to view a dashboard as John Smith would make checking user access very easy. ... View more

While it is possible to Lock a filter so that users can't change it, sometimes they get confused by the presence of that filter and want to try to change it, which results in a support call to us.  There could also be times when the filter criteria itself is sensitive. We should be able to right-click on a filter and choose "Hide from Viewers". This would also have the benefit of cleaning up the user interface a bit, so viewers don't have to wade through criteria that they can't control anyway. ... View more

Recently, we were trying to create a widget using the RPAVG function for a rolling 30-day average, which broke our connection to the live model while working (to an extent) on an elasticube. The function worked past the first 30 days on the elasticube, while the first thirty days were (SUM N )/ N. This formula works past those thirty days, but for the first value, for example, gives simply the first value.  A new version of these functions would be greatly appreciated.  ... View more

It would be helpful to choose where on a dashboard to add a new widget rather than it only being added to the bottom of the dashboard. ... View more

1. View all history of builds and its corresponding logs from the cubes. Because, I could not see the last build failure reason, if another build got started. I need to wait for another build to complete or fail. 2. View all history of changes and provide a way to revert as in Google docs for both the cubes and dashboards. Some times, if something went wrong, we should just be able to revert to the previous version and continue from there. 3. Provide a way to view the list of cubes in the queue waiting for the build. Also, allow remove or disable them for a period or rearrange the queue to build. This will help in prioritizing something manual on demand. 4. If a cube build fails due to the memory or other configurations issue, provide suggestions like what has to be changed and based on what before triggering another build. 5. Provide a page to derive the suggested the configurations like memory, cpu, timeouts etc by collecting details like 1. Number of cubes, 2. average cube size, max cube size, min cube size, or number of cubes by size range say <5g, <10G, <20G, <40G etc.., 3. Frequency of the build per cube etc.. 6. Provide a page to view all the slow running dashboards, slow running queries and some suggestions to improve it. 7. Some times, if a dashboard got changed and republished, it is not getting applied to all the users. Provide a way to view the version of the dashboard the user may view. 8. Between builds, if there is not much change in the data, Sisense build should go faster. Provide a way like one common place to build each table from other sources individually and keep it ready. From there, if we build say functional cubes, it should build in flashing fast using the locally stored data. I see the cubes are pulling the data faster from relational db but very slow from mongodb. Now, if we are pulling data from another sisense cube or from the source no big performance difference. 9. Also, I am not sure, if we are restarting the nodes, should we necessarily mark the cubes in queue as failed, instead adding back to the queue as it was before the restart and just marking the actual cube got failed should be good enough. More later .. Thanks, Muthusamy J ... View more