Hi It's a need that we have found many times, related to the availability to design the dashboard layput with a dinamic grid, not just columns and widgets in the same column. Users demand more flexibility on the layout design. ... View more

Our users often unnecessarily/mistakenly create filters at the Widget level when, really, it may make better sense for that filter to be applied at the Dashboard level. Had a suggestion from a user yesterday to add a menu button for Widget filters that will move/convert the filter from the Widget layer to the Dashboard layer. It would simplify the dashboarding process and make it quicker, less complicated, and less error-prone for end users. ... View more

Would like to have the ability to share multiple dashboards at one time instead of 1 at a time. Moving to Sisense from another software and having to share 50+ dashboards is very time consuming. ... View more

When building dashboards, a common frustration is the lack of ability to multi-select widgets and perform mass actions, such as moving a group of widgets all-together at the same time, or deleting multiple widgets at once. Currently, to do either of those actions, you must do it one-at-a-time on each widget individually. This is tedious and time-consuming if you have many widgets you need to move or delete. It would be nice if there was some way to select multiple widgets at once and perform some kind of mass action on them, like click-and-drag to reposition, or to select "delete" and delete all selected widgets at once. I'm not sure what the best way to do this would be. Perhaps a toggle at the top of the dashboard that allows you to click a checkbox next to each widget. Similar functionality already exists for the main dashboard list, on the left-hand sidebar...a toggle at the top will cause checkboxes to display next to each dashboard (or dashboard folder). Checking any of the boxes will cause additional options to display at the bottom of the sidebar, allowing you to export or delete the selected dashboards. Alternatively, if there were a way to "group" widgets into a container of some sort, then you could perform an action on that container which would apply to all widgets within it. For example, if you had a container, and then three widgets inside, you could select the container and move it, which would move the widgets as well, or you could select "delete" which would delete the container and everything inside it. ... View more

The behaviour of the From/To date component appears to be causing a lot of confusion new users - we have had multiple reports mis-selecting dates and/or thinking this is a problem with Sisense.   The problem appears to stem from the way the focus is automatically shifted to speed up input of the 'To' date. This is not expected by new users and causes confusion. When a date is selected in the 'From' box... If no date set in the 'To' box, move focus to 'To' box and allow the user to immediately select the 'To' Date If date already set in 'To' box, do nothing. So, the first time you set the date range the first click sets the 'From' date, and you can immediately set a 'To' date with a second click. This is handy, but at the same time confusing if you don't realise what it's doing, and in practice is causing complaints. ... View more

We embed Sisense into our application and produce pre-built dashboards for customers (which they cannot edit). We allow our users to create their own dashboards as well and with this comes the ability to create their own formulas. We have found that allowing them to edit the name of their formula also allows the editing of our pre-built shared formulas and our attributes. While this only impacts the user locally, it can become a support nightmare, as customers can rename our pre-built items and make it hard to them troubleshoot. We would like the ability to make these edit options more granular so that we can control (1) Shared Formula name edits (2) Attribute name edits and (3) non-shared Formula, local user dashboard, name edits. ... View more

Within dashboards, the only way to know currently if there is a filter on a widget is to open that widget. This is VERY time consuming if there are multiple widgets within a dashboard (we sometimes have up to 10). Please add an icon at the top of widgets (near the pencil would be great). If the icon is grey, no widget level filter is set. If the icon is colored in, a filter is set. If a filter is set, mousing over the icon should return a preview of what the filter is. ... View more

The email schedules have a limitation when the file used in attachment is large in size. Most email servers have a 25mb max limit.  It would be really helpful, if there was an option to include a downloadable link in the email. When a user schedules an email, with the link option, the attachment is downloaded to a temporary path and the link to that path is provided in the email. Clicking on the link should download the file from the temporary path which can be an s3 bucket or from some server. We can keep a retention policy of few days for the files. ... View more

Currently, if we export the pivot as an excel/csv, there is no indication of the date range it was run for in the output file. It will be really helpful to have control on the exported output in excel or csv, such that we can include the date range of the result or other filters applied in the output. ... View more

Upon receiving the warning "Maximum number of series (50) exceeded", the warning does not reappear with a widget, dashboard, or page refresh. Instead, a filter change is required in order to trigger it again. IMO the warning should persist with refreshes and be visible every time due to the impact of the limitation being exceed - data is literally missing from the widget and the widget does not reflect the data set expected by the user.  To that end of being clear about the impact of having more series than the limitation allows, the warning would be best reworded to indicate that impact and avoid users making decisions on an uncontrolled subset of data. For example, "Results limited to maximum number of series (50)..." or "Data limited..." This limitation should also be documented in Sisense documentation, but is not currently. ... View more

We produce pre-built dashboards for our customers.  They can build their own as well.  Often, they will start with one of our pre-built dashboards and modify to their needs. Users want a way to "filter out" our pre-built once they have created their own.  One mechanism mentioned was the ability to "Favorite" a dashboard and have a new "Favorites" toggle on the Analytics tab. ... View more

Hi, Whenever an user with owner access is deleted, all the dasboard created by him are getting deleted. Also, those dashboards shared with others are also deleted. This looks like a critical issue, since the dashboard will be shared among other users, they won't be able to see any dashboard if the user gets deleted. Atleast the dashboard shared with other users should be retained.   Thank You, Deviprasad ... View more

This is a request to enhance this feature in community thread of the same title. This is useful because it allows users to see all the available dimension for a particular list of filters even if there are no facts for it. I understand that we can also use this community thread; however, this is only limited to 1 dimension. However, right now, it does not work when [Columns] field are added into pivot table. We would like to add a date/day [Columns]. Ideally for us, the left outer join should only be by the [Row] and allow data to be broken into [Columns]. ... View more

Goal Enable dynamic alerting based on history using formulas Enable reuse of conditional coloring rules for pulse threshold  Background Pulse allows you to trigger off of a threshold (e.g. > 10,000, <= 10) Conditional Coloring of widget values allows for functions (e.g. Min([Months in Date], [# of unique Transactions]) Perhaps the Automatic anomaly detection does this, but we have no visibility into what is results in an anomaly.  Also not sure if you have to wait for the anomaly detection to learn. e.g. the cube has been built every day for years and has years of data, but the widget was only created a couple weeks ago and the pulse alert was added yesterday.  Will it detect anomalies or out of bound conditions that we could write with a formula Desired Functionality Enable use of functions in Pulse thresholds similar to Conditional Coloring of widget values Ideally enable reference to the Conditional coloring options for the widget.  The dashboard designer already built it into the dashboard. The user just wants a pulse alert when the widget turns RED.  Provide means of selecting from existing conditional coloring rules (Whether they are static values or forumlas) when building/editing the Pulse tile. ... View more

We find our clients sometimes using the widget information (i) button to provide their users with context for a widget. Their users sometimes click the button in search of information even when the designers haven't added any text to the widget information button. It would be helpful for end users to have a way of knowing before clicking that the widget information does or doesn't have additional information about the widget. ... View more

Hi, There are many widget types that are part of the core of an analytical solution. Examples like Tabber, Jump to Dashboard, Accordion... are tools that the business users find very powerful and gives Sisense the fleixbility in the visualization that put the platform in the road to copete with powerful visualization tools like Tableau. But, the profile of most of designers are business analyst or business users. To use and to configure properly this kind of visualizations, makes them to enter in a Javascript world, that it's very confusing and dirty. It makes that the promise of "self service" is not to close. I should be great if the configuration of this kind of visualization will be made from an user interface, without the need to write JS code.  Best ... View more

I would like to see some improvements regarding the pivot table in Sisense: Measures as rows Right now, when you add multiple measures to the pivot table they are automatically added as an extra column. Every major player in the BI business allows for measures to be added as rows, I would like Sisense to do so as well Expandable dimensions (could be used for almost every widget type) Let's say I have a pivot table showing revenues with categories as rows and years as columns. Ideally, I would like these to be expandable, i.e. if I click on the + icon for years, it should show me the quarters, months and so on. This could also be implemented for line, bar and column charts.  For categories e.g. I would like to expand to sub-categories. The drill-down we have right now doesn't work, it zooms in on just 1 category losing an overview of the data.    ... View more

---Summary:--- When you jump to dashboard, your dashboard filters are carried over to the destination. I want to also carry any Drill Into breadcrumbs. ---Example / use case--- I right-click on a FieldA row in my PivotTable and drill it down to FieldB. Then I click on a number to Jump To Dashboard. The destination filters for the FieldB row I clicked on, but it doesn't filter FieldA. That's fine when FieldB.value occurs only as a child of FieldA.value. But some of my FieldB items are repeated in several FieldA items. For example: Many cities have a "Main Street". I right-click and drill-down on New York's street names. Then I click on data for Main Street to jump. The destination dashboard will show data for every Main Street in every city, instead of just New York's. --- Can you make JTD respect such a drill-down? --- PS: I also made a request about making Drill create dashboard filters. That would partly solve this request, but not fully: Sometimes, I don't want Drill to create dashboard filters, but I will still want the Drill to be respected by JTD. ... View more

Opening a dashboard which leads to a temporary error will redirect the user away from the dashboard URL to a 'dedicated' error page, e.g. 'https://xxxxxxx.sisense.com/app/main/error?status=404'. If this is a temporary error and the user refreshes this page they will never return to their intended destination - they are stuck on the error page forever. This causes confusion for our clients. Is there a way to change the way errors work so that I'm not redirected to a 'dedicated' error page and instead I can refresh the page and see my intended dashboard once the error is resolved? ... View more