Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. 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:
I say No. The original approach is more convenient and can get the job done with fewer clicks.
Sorry but this not have UX !!! Please. Not GO !!!
I wonder how many times we have to repeat the complaints of inefficencies and requiring more effort to do the same work? These comments have been coming in for a year now, but MS persists in going down this design road.
Thank you for taking feedback from the community on the On-Object Interaction Feature; love the willingness to always improve 🙂.
The recent updates to the feature, particularly in the November 2023 version, have definitely improved the tool. However, I have decided to continue to turn it off because it is not as intuitive as working without it.
More specifically, my main reason for not using the feature is that it requires more effort to create a visual than not using it. One of the recent updates allowed the fields pane to be expanded so that all text for fields/measures could be viewed. However, when trying to add data to the visual, the second pane cannot be expanded. This is very limiting and it would be great to add the expansion feature to this level (See red highlight in image below showing where the user cannot expand the pane)
Yany
I've always really appreciated the new BI updates, I've been using Power BI since 2008 and for me a big difference are the monthly updates, but the "On-object interaction feature" was the worst experience and disappointment I've had, and they are already months and months of failed attempts at updates that simply don't make the experience better compared to the current one, so I always return to the default by turning off the feature. There is no way to be productive using this preview.
I gave it a few months of updates and tried it for 2 days after the Nov update. Turned it off again out of frustration. It's breaking my workflow and slowing down development considerably. I realize all I'm trying to accomplish is get the settings set up to try and emulate the current functionality.
Very sad...
Each month I try to use it and every time have to turn this off.
It's like as if who develops it doesn't use it at all. Otherwise they would experience all kinds of problems:
* "build visual pane suddenly collapses when clicking on an object other that visual and it takes extra click to get it open again
* "Build a visual" and "format" are two separate panes (instead of one) that take screen space so the report is smaller.
Turn off again
Similar results with me. While I'm forcing myself to use the new interface, I experience random issues, including pinned panes closing. When I'm in a crunch to get work done, I revert to the old interface to avoid confusion, aggravation, and impediments to progress.
Hard to turn it off again. This is just too awkward and as noted in a few of the replies to related post Re: Share your thoughts on the new On-Object Inter... - Page 2 - Microsoft Fabric Community .... completely random functionality is missing.
Hi There, apologies if this has been shared already, when using the on-object interaction i couldnt seem to change my values on a matrix visual to % of Column Total, usually under the Show Value As option this was there, but it wasnt showing any show value as options for me (or similar) while using this preview feature. Once i turned this feature off i could access these options again using the same columns in my data
This feature brokes my Desktop so I wasn't able anymore drag&drop column in visual field list. I had to turn the feature off to be able work.
I have experienced some annoying situations with this functionality, despite insisting on its use or stubbornness.
For example, in a project where a colleague has applied the implicit calculation to a measurement, transforming from "total" to "percentage", using "Show value as > Percent of grand total", when this feature is enabled it is not possible to do this.
1- using PBI with disabled on-object interaction, is possible change it:
2- when it is enabled, is impossible:
I am not fan of this feature, but it seems to me you can simply right-click on the field and change it, screenshot below with it enabled >>
I'm not fan too, but I'm just supporting a project.
I have a doubt about your screenshot: are you using any field in the table or a measure that calculates, for example, a distinct number of records (like the case I took)?
I don't have access to PBI to test right now, that's why I post here.
I tested both sum(amount) as measure and as field, on table and bar chart visuals, it works, give it a try when you can, although any measure needs to return a scalar value, not a table for it to work on a chart.
I really don't know how to explain why, but I can't do this when the feature is enabled.
If I use the column then I can apply some aggregation, for example, "Count" or "Count (Distinct)".
However, using a measure that makes the DISTINCTCOUNT (like previous aggregation) and then applying the "% GT" is not possible using object interaction, only if I disabled it.
I just tested creating a new look and even with it I can't do it.
X-Axis goal lines are not allowed either. It is only possible without OnObject Interaction.
Here's another example, thanks!
I was just watching a video on DAX Query View by Marco Russo and even he had problems with the new interface (for 30 seconds).
That speaks volumes.
Please change the navigation buttons on the pane switcher. It is awkward at best.
The X in the pane switcher is huge pain in the neck!
I find myself constantly opening things that I have inadvertantly closed.
The user experience would feel better if the option were to simply collapse the pane only.
What exaclty is the use case for closing a pane versus collapsing anyhow? It is not memory hog. Closing it does not appear to offer any benefit except enabling users to have to click twice more time to get to open again.
The current user experience for this is backwards.
Two clicks to collapse, click again to re-open; and, one click to close, with two Clicks to re-open.
I recommend one clicks to collapse, click again to re-open; and, two clicks to close, and two clicks to re-open.
That is, unless you can somehow make it so that there is ever only one click, like getting rid of close altogether.
I suspect that most would agree that collapse should be the primary action and not close. If nothing else, give me a collapse button! I should not have to click twice to collapse the pane out of the way.
Great news - we're swapping the default behavior to be collapse instead of close with the new default configuration planned for December. Check out the November blog update that has the list of what to expect for December's new default.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
87 | |
76 | |
74 | |
55 | |
45 |
User | Count |
---|---|
117 | |
106 | |
77 | |
66 | |
65 |