Lock out selection of shapes and widgets
Shapes are useful for adding background formatting to pages. However, if accidentally selected, they move to the front and obscure anything in the same location until deselected. This can be very jarring and confusing to viewers.
PowerBI should allow marking a shape as 'locked' to prevent interactions in View mode that would trigger this behavior.
David PROVOST commented
This bug is the main reason why we can't implement a slicer pane (see https://www.youtube.com/watch?v=xy9nmSQeUWg)
VERY MUCH NEEDED
John Mackenzie commented
There are a ton of suggestions like this - really hoping it gets noticed and changed
Howard Fulks commented
Completely agree. This should be a bug and not a feature request.
I strongly recommend this idea. I have been facing this issue for at least a little more than a year!
Michelle Merchak commented
Personally, I think this should be general for all visuals. Once out of edit mode, the Layer Order should be static, no matter what is selected. If I have set a visual to be behind another, it is for a reason and should never appear in front of it! It's quite odd behavior in my opinion.
Without this, interacting with visuals that include shapes becomes a very confusing and unprofessional experience
Benjamin Swift commented
Really we're missing visual formatting options which would make a lot of this unnecessary (e.g., shadow).
James Houck commented
This feature is absolutely a must. Users think they did something wrong when a background shape gets selected and moves to the front of a visual. The workaround is to not use shapes, but then, why have the shapes? They are great for design, they just need to allow turning off any hover over or select ability. I can't think of a single use case where you would want this to happen, so it seems like a bug to me.
I would actually add this as a "General" setting for all visualizations that would be called "Allow Interaction". When enabled (default) the visualization behaves as it does today. When disabled, the visualization is non-selectable and cannot be interacted with. Using that, it would be trivial to setup some UI elements and have them not be bothersome in production reports.
This has been a feature of other MS programs for a while - it's like the old "Locked" and "Disabled" combo in Access.
For graphics, informational text, etc., having them be selectable outside of edit mode is a nuisance. It not only makes for a broken UI experience, but it also can cause a lot of confusion when you're trying to interact with a graph that has some image/etc. behind it.
It's one of the user's complaints. It's important to allow the 'lock' option and no confuse the users.
as a designer, I struggle with this right now, it would be an awesome thing if you could 'lock' the shapes so no one can click on them
Wow! I suggested similar feature yesterday. Was redirected to this post. You made this post LAST year! :D
MS has still not responded or even acknowledged that its an issue! :(
I lost all hopes now
Qlikview is winning over PowerBI, as each day passes I am losing arguments with my colleagues on why we should switch to Power BI :(
Good idea, Aaron. Our users get confused when an entire tile disappears because they clicked on an element we use in the background for appearances only. We also have issues when users hover over a tile, and the outline of the tile appears. It obscures other elements (text often). We spend time to make the reports visually appealing and need the ability to keep them this way.