ContributionsMost RecentNewest TopicsMost LikesSolutionsDependent Filter Reset When using dependent filters and selecting new filter values this automatically resets all filter values already chosen. Whilst this is desirable from a security perspective, not all models have security applied. The proposition here is to have a toggle or similar that the designer/owner of the dashboard can use to turn this behavior on/off. Thus the reset reasoning behind this can be maintained if required for that model or use case and the behavior can be turned off if non resetting is optimal for the use case needed. Re: Folder and Dashboard Ownership for Multiple Users Thanks Benji and Laflet - this is great that you have / there is something like this, however we feel this should be something that is part of the core application rather than being an Add-On. Other BI applications have this as core functionality. DRay - Your thoughts on my previous comments? Re: Folder and Dashboard Ownership for Multiple Users Hi DRay , Will users be able to move co-owned dashboards into each others folders and republish? Because if not and if folders cannot be co-owned then it means that dashboards can only be co-owned outside of folders which in some ways defeats the whole purpose !! Re: Folder and Dashboard Ownership for Multiple Users Hey - That is great to hear, will this also encompass Folder Co ownership? Re: Filtered Perspectives Hey. If we take the example of a model that contains Tickets, both Open and Closed. We have dashboards that only look at Open Tickets. So applying Security is not applicable because the users have access to both Open and Closed tickets. Creating Security would stop them seeing Closed tickets on other dashboards they have access to. Adding a locked Filter onto a dashboard doesn't look great, it can often confuse users who need explaining what a locked filter is. Further, we would then want the values available in other filters to be limited which they are not. Adding a filter at the Perspective level takes away all of this in that a perspective of data is not just the reduction of fields but also the tailoring of the dataset. I am not sure if this also has some runtime/performance advantages, e.g. if the data is limited at the model level then there is less for the dashboard, widgets and jaql (e.g. for Filter values) to have to process, this may be marginal, but may be significant in some very large models. Folder and Dashboard Ownership for Multiple Users Folders and Dashboards are only permitted to have 1 owner, this has been the case with Sisense since we first started using it 6 years ago. The time has really come to allow multiple owners of Dashboards and Folders. We have around 70 Designers who use our Sisense instance and being able to swap work, work jointly, used shared structures etc. adds a huge amount of time, inconvenience and frustration. The request here is to allow multiple owners of Folders and Dashboards so that Designers can collaborate more effectively, the flexibility of such work would greatly reduce the time to deployment. Filtered Perspectives 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. Chart labels with different format to Value label When formatting a value on a chart to, for example, a percentage with 2 decimal places, the axis relating to the value will also show as 2 decimal places. Having an axis with 10.00%, 20.00% etc does not look good. There are scripts that can potentially overcome this, however they are as all such scripts unsupported and prone to break on upgrade. This should be part of core functionality where the Designer is able to set a number format that precludes this from displaying. Manual Sort of Series and Columns Currently sorting of dimensions/categories/series is by Ascending and Descending only. There are times when such data points need to be sorted in a non alphanumeric manner. For example, Critical, High, Medium, Low is the desired sort, but this appears as Critical, High, Low, Medium or Medium, Low, High, Critical which looks sub optimal to the user. A workaround is to add a number prefix via modelling, again this is less than ideal for the user, as is a script to update the displayed values to remove the prefix. As is possible with other BI Tools, there should be an option for the Designer to configure the sort. There are various community plugins and scripts that do this on an explicit per widget basis, however these are prone to fail/break and aren't guaranteed or supported through version upgrades. This should be a part of core application functionality. Enhancements to Pulse We have some ideas for enhancing Pulse: Once a Pulse alert has been created, have the ability to edit the filter from the Pulse page. Have the ability to create Pulse as an option from the entire dashboard. Users would select a measure for the pulse and set filter conditions from the model in question directly. Make the Pulse input pop-up available within the application for developers (e.g. 3rd Party) to exploit from plugins they have developed. Add ability to configure Pulse to trigger on a schedule (once per day, once per week, etc.), e.g. when a build is done, the alert gets sent according to the schedule. Option to set Pulse to trigger when value changes in any direction rather than having to set up a specific calculation.