When utilising the Fiscal Year functionality, it is frustrating that there is no option to display the calendar year as a formatting option. We are based in Australia and our Fiscal Year starts in July, so our 2023/2024 Fiscal Year (called 2024) runs from July 2023 to June 2024. If I create a simple pivot with our Date, Year (Calendar Year formula) and Fiscal Year (formula in format YYYY/YYYY), then you can see that the date is actually distorted.  There is no way to display that this date actually falls in 2023, which is the case for the first two records in the below pivot. Applying a filter with a date range handles this correctly, but it is confusing for our Finance department as to what date this is referring to. I've connected with Sisense support and they've provided a solution for a Date Display Field (thanks @AssafHanina) which does solve the issue, but then we need to have complicated rules for dashboard designers to use X field on their Dashboards but Y fields on filters, etc. I feel like an additional date format of "cy" for Calendar Year would solve this issue from the display side and make things much simpler.  Some logic already exists for "yp" for the previous year, this would be very useful for our designers to have this additional option and to keep the date as one field rather than needing a second. Has anyone else encountered this issue or would find this useful? ... View more

Hello, It would be good to be able to export data to Excel from the Dashboard menu. Currently, one dashboard containing 3 widget requires to go to each widget and export to Excel, resulting in 3 diffrente Excel spreadsheets. Users are requesting to be able to export every widget data into one single Excel file / each data widget in one seperated tab. This features exists in ReportManager, so it is difficult to understand why it is not available from the dashboard view. Thank you and regards, Franck ... View more

Currently, the aggregation function depends on the type of the dimension : - Text or date => Distinct count - Numeric => Sum In our use case, this default assignation is not always accurate as it is sometime required to use Distinct Count with numeric fields. It would be good to hauve the default aggregation function to be choosed by the cube designer, when developping the metadata layer (ElastiCube or Live cube). This way, the dashboard designer will be proposed the accurate function without need to change it. This is particlary interesting with a users population that don't have analytics background and for which choosing the correct agregation function is not obvious. Thank you ... View more

Looking for a way to change the logo based on their corresponding theme. We can create themes for the different companies but there is no option for logo in the Theme and would like to capability to extend the white labeling past just 1 logo ... View more

When a widget returns no data and is displayed in column format - it would be nice to have an option to show the column headers only to give users a reference point as to what data will be shown. Thanks ... View more

Perspectives is a great addition to the application and making only certain parts of the model visible to those dashboards connected to that perspective is excellent.  Adding the ability to filter the perspective is something that is required for many of the use cases we have.  For example, we have a model that has All Tickets.  We have many dashboards that have a locking filter at the top to show only Open Tickets which doesn't look good from a user and design point of view.  Being able to create a Perspective and not only be able to refine the columns but also filter to (in this example) Open Tickets only would greatly add to the power and usability of this feature. ... View more

The idea of this is so you could show the elasticube data on the primary axis, and then potentially low latency data on a secondary axis - allowing easy comparison of live vs historical data ... View more

We are a multi-tenant software provider and we embed and white label Sisense.  In our setup, we have 2 models.  Model 1 is used by Engineering to create our pre-built dashboards, where we share these with specific groups we've set up so that all of our customers see our pre-built "out of the box" dashboards The second model is what we expose to our Premium users so that they can create their own custom dashboards.   There are times when our customers will create a new, custom dashboard with the second model.  These users sometimes share their dashboard very broadly.  When this happens, there are certain users that wish to remove themselves from the share.  Perhaps they don't have row-level security to see anything.  Perhaps they have changed roles or simply do not use that dashboard. Note that we do not want to allow customers to remove themselves from our pre-built shared dashboards, as this could cause support confusion as to why our analytics solution is enabled but a user doesn't see "all of the dashboards".   With the above noted, we would like a configurable means to show/hide a "leave shared dashboard" dashboard option, based on the model with which a dashboard is associated.  This will ensure that users cannot remove themselves from our pre-built dashboards (we would hide on our model) yet allow them to remove themselves from custom dashboards that were shared with them (we would show on model 2 for self-authoring) When a user leaves a shared dashboard, there should also be configuration options to alert the owner of the dashboard via email.  This email should be capable of white labeling.  It should include dashboard name, who left, and when.  Should there be links to the dashboard in the email, there must be a way to disable hyperlinks in the email. ... View more

As a standard offering, enable color conditions to also be displayed in the Grand Totals columns/rows. The coloring should also carry through to Excel or pdf downloads, the same for the rest of the pivot table.  Current custom script solutions are at risk of breaking with future version updates, and the Grand Totals colors do not carry through to Excel and pdf downloads. ... View more

When creating a widget in SimplyAsk, We would like to see the download option extended to offer exporting to excel/CSV if the table viz is the best option. Some viewers might not be able to pin it to the dashboard but still want to extract the insights.  ... View more

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** The Data Designer, when modeling an Elasticube or Live model isn’t able to define the default aggregation method. When adding a measure to a widget, an aggregation method is automatically applied. The Dashboard Designer can choose the aggregation method via a menu, but a regular click will always choose a predetermined system-wide defauilt (distinct count or sum). In some cases, the aggregation applied is not relevant and could lead to invalid results. I would like to see a feature that allows a Data Designer, when designing the data model, to define the default aggregation for a column. A Data Designer has the knowledge of the data model and what aggregation is best used for it. This ability would assist Dashboard Designers in correctly using the model. ... View more

Currently, it appears that Shared Formulas are displayed in the selection dialog based on the order they were created. It would be great if they can be arranged logically, or at least sorted alphabetically, otherwise the list can grow to become disorganized and difficult to use. ... View more

Currently the Analytics screen displays available dashboards in a "list" view or a "tile" view.  The "tile" view includes columns "Name", "Owner", "Data Sources", "Last Published", "Last Modified", "Total Viewers", "No. of Widgets".   This is a request to add a new column "Source Folder".  This would be helpful for users with a large quantity of dashboards as they could sort by the "Source Folder".  In the future, the list view functionality could be expanded to allow grouping by this column which would further consolidate the view. Thank you! ... View more

I recently posted a query on sisense forum to increase the offset size of a pie in a piechart. I got a response how it can be done at a widget level, but there is no feature in sisense to apply this change at global level for all pie charts in every dashboard. In fact, there should be a global space where any change for any widget could be applied to all such widgets in every dashboard. ... View more

When filtering on a numeric field and using a Value type filter, I often want to filter on a dynamic value. As the Ranking type filter can take a formula, I would make good use of a Value type filter that also allowed for a formula. ... View more

The idea here is to expand the formula editor (Specifically CASE WHEN Statements) to allow the creation of dimensions or "buckets" based on filtered data. This is useful on the dashboard level as we may want to recategorize our data dynamically after filtering the dashboard.    Lets say I have a pretend table holding daily customer transactions. In my report I'd want to see each customer's average spending for an arbitrary time frame. I'd also like to categorize that player BASED off that average spending. Which could change based on any filters I use.  IE)   CASE WHEN [Avg Money Spent] > 999 then '1000+' WHEN [Avg Money Spent] > 699 then '700 to 999' WHEN [Avg Money Spent] > 399 then '400 to 699' ... WHEN [Avg Money Spent] >= 0 then '0 to 99' ELSE NULL END   I would then use this calculated dimension in visualizations like pie charts, etc. I'm not sure if this is possible, but being able to use this dimension as a filter would be very useful as well. IE) Show me all the customer who fall under '400 to 699' range for any given period. ... View more

We need a view that shows us which dashboards are dependent on which table in the datamodel. We want to remove some tables, but because we have many dashboards we don't know where exactly that table data is being used so it's very risky to change/delete tables. The depedency granularity of the data model is good but not enough. ... View more

---Summary:--- When you drill, create a filter. Link new filter and the drill-breadcrumbs, so if you change one, it changes the other. Make it an optional, per-widget setting. ---Details:--- Sometimes I build a dashboard with a "main" widget for the user to explore, plus a few indicator widgets above it. It'd be nice if, when the user drills on the main widget, their choices were applied to the dashboard filters. That way, my indicators would reflect what they've drilled into. But that should be an option in the widget settings; other times I have a dashboard with several major widgets and drilling into one should not filter the others. When the user un-drills (clicks the cross or a breadcrumb to return to the overview), that should automatically remove the associated dashboard filter. And if the user alters or removes the dashboard filter, that should carry over to the drill-down breadcrumbs. ... View more

Problem: Users commonly wish to share data with their team members, but reports with many filters can be difficult to reproduce and share with others while abiding by security permissions. This causes confusion when numbers appear different, but the result is simply that the users are comparing data with two different filter sets applied. Summary: Saved searches would allow for users to create filter sets across multiple dashboard filters to quickly return to a filtered view of data. These saved searches would also be highly beneficial if it allowed users to quickly share these filter sets with users that have access/permissions to the dashboard of origin when the two users are both part of a user group that allows filter sharing.    Admin User Story: As an admin, I would like to create a saved search that allows users to see data for each region of the United States for the current year-to-date as well as saved searches for each quarter of the current year. I don't want to create multiple dashboards or even multiple widgets as I'd like the user to be able to see consistent stats for each time frame.  The admin creates a saved search for each of the desired filters to allow a user to quickly navigate and select the different saved searches to populate multiple filters at once with the desired filter set.  The admin has access to share with all users, but they decide to share the filters with the Executive user group. In order to share with the executive user group, the admin must enable filter sharing within this group. The admin as well as members within the executive user group will be allowed to share with all members in the executive user group once this permission is enabled.  After enabling filter sharing, the admin shares the filters with the executive team. The admin can choose to include an email or only share within the system with no notification. They decide not to notify all users of the group, but they copy the share link for the 3rd Quarter Western Region saved search. They send an email to the director of the West Region with the saved search link. (See Viewer User Story)  Viewer User Story (West Region Director): A viewer belonging to the executive user group receives an email from their Sisense admin including a link to the 3rd Quarter Western Region saved search. They click the link and are directed to the new strategic dashboard with the filter set for the 3rd Quarter Western Region applied to the available filters.  The viewer reviews the data and reviews the other available saved searches for the additional quarters that were provided by the admin. The viewer clicks on the 2nd Quarter Western Region and the filter set populates in the filter pane.  After reviewing the filter sets provided, the viewer adds regional subdivision filters based on the territories of their Western Region managers. The viewer creates the "West - Territory 1  (Q3)" saved search and shares it with their West - Territory 1 manager only and sends a notification to the manager. In addition, the viewer identifies issues with two specific teams and filters to these teams in the manager's territory. The manager filters to the two teams as well as the product's where issues were identified. The viewer saves the search as "{Manager Name} - Quality Assurance Focus" and sends a notification when sharing the search to the manager. The saved search allows the manager to quickly highlight focal points with his manager so that the manager can review the data the director sees prior to meeting and discussing the issues at hand.       ... View more