ContributionsMost RecentNewest TopicsMost LikesSolutionsRe: Folder and Dashboard Ownership for Multiple Users YuliyaMotiyetsthis is encouraging - right now this is causing real problems for us in production. There are several important use cases for this folder system - UI presentation to end users, asset organisation and dashboard publication & basic version management. Items 1 and 2 are high priority, 3 should really be there but less important than the other two. Folders are invisible to other admins if the dashboards that contain them are not shared. This creates a situation where multiple versions of folders or dashboards (even with the same name) can be unknowingly created. Only the owner of a folder can add/remove dashboards. Proper organisation/versioning of assets can be almost impossible without reassignment of dashboard ownership. Not possible to move folders. It's really time-consuming to create a new empty one, drag each dashboard individually and delete the old one. Re: Filter only on Weekends or Weekdays Thanks Jake_Raz, this was my first choice - really, I'd prefer to do this in UI layer to avoid adding maintenance in the model, but I'm not sure it's possible without changes to formula interpreter (unless anyone knows different!) Re: Filter only on Weekends or Weekdays Thanks AssafHanina this might be a way to go, need to think through best approach if we go this route. Filter only on Weekends or Weekdays I have a need to filter based on day of week - for example, I need to total all weekend (or weekday) sales. The filter would seem to be the way to go, but I can't find a way to get it to filter based on weekday. I tried JAQL exclude, which it parsed ok but didn't seem to work correctly. Any other ideas? SolvedForecasts for multiple series to pivot table The inbuilt forecast is useful for projecting forward, but only handles one series on a chart. Is there any way to break by customer direct to a pivot? This would answer one of our use-cases very quickly and easily. SolvedRe: Ability to disable (but not delete) users Hi DRay , understood - this is still very much on our wish list. For additional context, we have accounts in our system that we might want disabled, but not completely removed (they might need re-enabling in the near future) - for example: Sisense support team member accounts demo accounts temp/test accounts evaluation accounts best practice is to disable accounts as soon as they are no longer required. This is far less risky and more visible to admins than altering global group or data permissions. Date picker UX is confusing for new users 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. Re: Ability to disable (but not delete) users Leaving old accounts active (even with reset pw) also represents a security risk. Given recent events, this should be reconsidered for implementation - I can't imagine it would be hard to do. Re: Two-factor authentication This is a security issue and has to be a high priority. Environments can be complex and SSO isn't always easy to set up for all users for a variety of reasons. Similar to others here, we have different groups of users that we need to tie into the system, which makes moving to SSO more challenging. MFA is standard now for good reason. I'd support the approach above of flexibility (authenticator/SMS/none) on a per user basis. Series should be selected (rather than disabled) when clicking on legend We have had several users complain that the way series selection for charts is not intuitive. Currently, when you have multiple series in a line chart and click on one in the legend, it gets disabled to highlight the others. The intent is to allow focus, but it's the wrong way around - most users expect that the item clicked should be selected and the others hidden. The current behaviour is quite painful if you want to see one series when there are several (you have to click on all the others). Is there a simple way to reverse the selection behaviour, or do we need to look at other options: wrap the control and handle it ourselves (possible?) build some drop-downs/UI to allow selection of whats shown some other neat UI work-around??