Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers!
Enter the sweepstakes now!Prepping for a Fabric certification exam? Join us for a live prep session with exam experts to learn how to pass the exam. Register now.
Hit Reply to tell us what you think about the new On-Object Interaction feature so we can continue to improve.
For example:
Thanks,
-Power BI team
To read more about the feature, see the announcement in the Power BI Product Blog or our documentation on how to Use on-object interaction
FAQs:
This is the first time I've turned off a feature in Preview.
1) Shortly after turning it on, my report started crashing with the Web2 error.
2) When I tried to test RLS it didn't work; I later realized it was working but was no soooo slow refreshing the visuals it appeared to not be working. I wasted 30 minutes troubleshooting...
3) I'm adding a button, just an up arrow, I want it to be yellow. The format menu is gone. Why does it keep closing on itself. I want it open all the time. I don't want to have to reopen the format pane constantly.
4) The pane to add fields to a chart is tiny (granted I like to work on my small portable laptop; I have monitors I can plug into but I prefer being mobile as I have kids and work at home on the weekends). The tiny list of fields is one of the things I hate about Domo. You're going the wrong way with this feature...
For these and other reasons, despite trying to use the new resource, I waste too much time, and I don't have time to waste. So after a few hours to analyze the "news" I return to the standard, which is much better and more intuitive.
ok got two usability issues that im finding annoying and not sure if im missing something.
1. i need to go to view then select element each time i close it, its a natural habit to close but close should be minimize, not shut down completely, isn't there just a way to miminize from the on object menu, and not shut that element down completely, it doesn't seem intuitive, maybe im not doing it right but having to go to the view menu all the time is annyoying
2. why is it so hard to find away to pin more than one element open, i literally cannot find the setting to have both for eg setttings and data open at the same time. sometimes its there othertimes not. I just want to pin certian elements open at the same time, something like pinning it, not trying to work through a myriad of settings that do or dont work same way each time you arrive there.
help
Proud to be a Super User!
I just had a comment removed as spam from a recent YouTube video about on-object interaction. My comment was short, intelligible, and had a link to this forum post. It was in no way trolling or spam. It was in response that the PBI designers "really appreciate the hard truth", and yet the comment was deleted. PBI Team, please don't implement this feature.
Maybe my suggestions here will offer the solutions you are looking for.
I'm finding this on-object feature more useable now that I'm able to have the panels on the side (like it should be) instead of on the visual (object) I'm wornking on.
I understand that receiving this withering barrarge of negative feedback leads to shell-shock, but the policy of "radio silence", just sticking your fingers in your ears and singing "la la la" will not change anything. If this feature is based on real-world research and user feedback, please be forthcoming.
If that does not exist, what is the driver behind this determined effort to piss-off your professional userbase? Drive us all to the online environment? There is clearly something bigger at play for MSFT to so willfully disregard and disrespect the userbase.
We really are going from disappointed to highly irritated with MS's position in relation to its worst new feature to date. The On-Object Interaction feature (preview) should have been left aside a long time ago due to not meeting the basic needs of developers (development agility = simple with just a few clicks).
The silence from MS on this is deafening. The lack of any attempt to shed light on why development seems to be determinedly proceeding in the face of what seems to be overwhelming and consistent resistance from the professional users is only exacerbating the angst we're all feeling.
Ok, they answered. Not in this feed, but rather via an interview from Guy in a Cube. I mentioned this in another reply, but it is becoming apparent that the developers for this "feature" are not interested in feedback from those who don't like or want it. They have their agenda and are pressing on whether we, the ones who use it daily, like it or not. The best we seem to be able to hope for now is that they allow us to turn off this "feature" once it becomes the default. I'm betting that they will for awhile, and then begin to phase out support/development for it to force us to eventually switch.
They have to hope that we don't switch to a competator's platform. Then again, maybe they're banking on there being enough "newbies" to PBI that don't know the difference to make up for the loss of those users who can make it shine. Dollar signs for the win! 🙁
Please read, analyze, think and review your response position regarding the negative feedback for this new feature. We expect objective answers as developers, we are becoming increasingly disappointed and angry. Do you want to develop something new? Think about doing something simple with a few clicks, so far we only have an increase in clicks on a visual that is only simple in your head, listen to the base if you want us to continue using and recommending Power BI, or you will see a flood of developers moved to other BIs, such as Tableau and others. We don't want that, we like Poer BI, we chose Power BI, so hear us out.
This broke the silence, but did not address our concerns in the least bit:
Why On-Object Editing in Power BI??? - YouTube
The worst part is that they confirm "it will become the default experience at some point." Time to start looking at other products...
It appears the MS is not interested in dissenting opinions about this feature. It will be the default whether we like it or not. Our only hope now is that they allow us to continue to turn off the "feature" once it becomes the default.
I completely agree. I always respond to the survey that appears from the BI service and I always gave my rating between 8 and 10, but today the rating was 5 and the explanation I gave was precisely an attempt to put down something that nobody wants, the new On-Object. Interaction feature (preview) is the worst one yet.
What people mean by “having a similar interface like other Microsoft products”, are actual useful functions, such as right-click Waterfall chart data column to “make total”, or on Scatter chart dots to customize color (the typical Excel right-click magic), which is non-existent in PBI today.
“On-object” is not attempting to do any of those. It merely reshuffles existing functions to many different places, making a mess with UI, while quadruple click-counts. It adds absolutely no value to users whatsoever, only big headaches.
I am not sure MS is actually listening, or just pretends to, but seriously, if you sort comments by seniority of “badge level”, you will find so much negative feedbacks from power users – a.k.a. active members of the community who have been helping average users day-in-day-out.
But why bother listen to them?
Of all the mistakes Microsoft has made for Power BI (and there are way too many to name), this is among the most cumbersome and least thought out.
Way to design something from a non-user perspective.
I appreciate your efforts in improving Power BI but for on-object formatting I really think it got harder to work.
Even though I have all the panes shown it seems like especially when trying to change the visual types it is not that intuitive and somewhat still buggy (sometimes things disappear).
Without saying that more clicks are needed to perform simple functions, I'm really losing hope that this will become productive, I hope that the default mode remains, it would be much better to include some good ideas of this new feature in the default mode, and stop trying develop this new feature.
Here's an idea. Why don't you scrap this fatally flawed 'feature' and put your efforts on improving the existing interface and functions. Like being able to lock individual visuals/elements on the page. Like redesigning that ridiculous Edit Interactions function (you have to move everything out of the way to turn off a buried visual, or hide and unhide. Also no way to bulk turn on or off that I can find).
I must admit the daily barrage of negative comments for the On-object interaction 'feature' have been a source of amusement for me as people TRY to be polite but often fail. I'm not even going to try. Get rid of it. Focus on some basic issues that people have been whinging about for years. Once you get what you already have right, then maybe experiment with something new. But you are a long way from that scenario.
Turning off.
I would like this feature if it didn't take away the ability to also use the visual pane for adding and modifying data fields. As it is, it doesn't seem possible to do some of the things the pane allowed for (e.g. the options to show data for empty is gone).
I had to turn this feature off immedtiately, it completely killed my build visuals pane. I couldn't edit anything. I had to find this thread to see what I had turned on that made it so I couldn't do anything on my report: https://community.fabric.microsoft.com/t5/Desktop/Build-Visuals-pane-missing-Power-BI-Desktop/m-p/31...
Note that there was a huge improvement compared to what was there before the October update, although it is still very far from becoming operational and generating any advantage compared to the current one. I also can't spend more than a few hours with this new feature enabled, I waste a lot of time and additional clicks to carry out tasks, which in my case are many and daily. Features disabled by default for me.
Check out the April 2025 Power BI update to learn about new features.
Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
User | Count |
---|---|
72 | |
67 | |
65 | |
42 | |
42 |
User | Count |
---|---|
46 | |
40 | |
28 | |
27 | |
26 |