Power BI On-Object Interaction - A Working Review for Report Builders

Power BI Desktop used to feel like editing a document while wearing oven mitts. You'd click a visual, then squint at the panes on the right, then drag a field across half the screen, then click formatting and hunt through accordion menus for the property you wanted. Repeat that 200 times a day during a report build and you understand why analysts develop opinions about Tableau.

On-object interaction is Microsoft's quiet rewrite of how you actually build a visual. Instead of doing everything through the side panes, you work directly on the visual itself. Click a chart, get options near the chart. Want to change the field on an axis? Click the axis. Want to format the title? Click the title.

It sounds small. In practice, after six months of using it on client engagements, I'd describe it as the biggest day-to-day quality of life change Power BI has shipped since incremental refresh. Let me walk through where it shines and where it still trips you up.

What changed

The build experience has moved from "tell the side pane what you want" to "manipulate the thing directly". When you select a visual, you get an action bar above it with the most common operations: change visual type, add a field, format, more options. Each of these opens contextually relevant controls right next to the visual.

The field wells are still there, but they're now part of an on-canvas pane that appears next to the selected visual instead of always being parked on the right edge of the screen. You can move it. You can pin it. You can close it entirely if you know what you're doing.

The format pane has had the bigger conceptual rework. Instead of one giant scrolling list of everything that could possibly be formatted on the visual, you click directly on the part you want to change. Click the title, get title options. Click the data labels, get data label options. Click the axis, get axis options. The format pane filters itself to what's relevant.

You can still turn it all off if you want. The classic side panes are one toggle away. We've had a couple of senior analysts who'd built reports for so long with the old layout that they preferred to keep it. That's fine, both modes work.

The bits that genuinely help

The big win is speed of small changes. Most of report building isn't writing measures or modelling data, it's the death of a thousand small tweaks. Move this title, change this colour, swap this field, adjust this axis range. The old workflow made each of those a 3 to 5 click operation. The new workflow makes most of them 1 or 2 clicks. Multiply that by the number of tweaks in a report build and you get back real hours.

The field swap experience deserves a specific mention. You used to have to drag the existing field out of the well, then drag the new one in. Now you click the field on the visual itself, hit "replace field", and pick from a list. It's the kind of micro-interaction that you don't realise was annoying until it stops being annoying.

The format pane filtering is the other big quality of life thing. Power BI's format options have grown to the point where finding a specific setting was genuinely difficult. There are dozens of categories under "Visual" and dozens more under "General". With on-object interaction, clicking the thing you want to change just shows you the relevant settings. It's not search exactly, but it's better than scrolling.

For new analysts, this is huge. We do a fair bit of Power BI consulting work where part of the engagement is bringing junior staff up to speed. The new interaction model is dramatically more discoverable. People can build a competent report after a day instead of a week.

The bits that still need work

The action bar position is occasionally annoying. If your visual is near the top of the canvas, the action bar appears below it. If it's near the bottom, it appears above. Most of the time that's fine. Sometimes the action bar overlaps the visual next to the one you're editing, or appears in a spot where it covers something you wanted to see. Not a blocker, but a small friction.

The "more options" menu hides things that experienced users hit constantly. Hide visual, group, edit interactions, sort by, all the things that used to be one click on a right-click menu are now two clicks (action bar, then dropdown). It's faster for beginners, slower for power users. After a few weeks you build muscle memory but there's a definite learning curve in the other direction.

Multi-select editing has lost some functionality. With the classic side pane, if you selected three visuals and wanted to apply the same colour to all of them, you could. With on-object, the action bar shows you the lowest-common-denominator options across the selected visuals, which sometimes means the property you wanted to change isn't available. We've ended up doing things one visual at a time more often, which is the wrong direction.

The format pane behaviour when you click on whitespace inside a visual is inconsistent. Sometimes it shows you the "general" formatting (background, border, title). Sometimes it deselects entirely. The rules aren't obvious. You learn them eventually, but in the meantime there's a lot of "why did that just happen".

How it interacts with your team's existing reports

This part matters more than people realise. On-object interaction doesn't change anything about how reports render for end users. It only changes the authoring experience. So you can turn it on for some report builders and not others, you can switch back and forth on the same report, and nothing breaks.

What does change is how you onboard new builders. If you're standardising your organisation on Power BI for the first time (we've done this for a few mid-sized Australian businesses in the last year), absolutely start with on-object interaction enabled. The discoverability win for new users is too good to skip.

If you have a large team of existing builders, give them the option. Some will love it immediately. Some will hate the change. The good news is they can flip back and forth without any consequences. Our experience is that the resistance lasts about two weeks, after which most people convert and stay converted.

The one place we've seen real pushback is with analysts who've built a workflow around keyboard shortcuts and right-click menus. The on-object experience is more mouse-driven by design. If your fast users have keyboarded their way to expert-level speeds, they'll be slower with the new interaction model and they'll feel that loss. There's no good answer here other than telling them they can keep the old experience.

A small but underrated detail

The "show data" interaction on visuals has gotten genuinely good. You can now click on a data point and get a contextual view of the underlying rows without leaving the visual. This used to require either drillthrough or a separate table visual. For ad hoc exploration, particularly when you're QA-ing a measure and want to understand what's actually being aggregated, this is much faster than before.

We've started using this during data validation conversations with business stakeholders. Instead of building a debug page, you just click the suspect data point and show the rows feeding into it. The conversation gets concrete faster. Whether you're doing this with a single analyst or a whole business intelligence team, it shortens the loop.

What I'd watch out for

A few practical notes from client work.

Custom visuals don't always play nicely with on-object interaction. Most of the big AppSource visuals (ZoomCharts, OKViz, Inforiver) work fine. Some smaller ones still show the old behaviour or have weird interaction quirks. Test before you commit your standards to a specific custom visual.

The new field replacement experience uses a flat list of fields rather than the hierarchical view in the old data pane. If your model has 200 columns across 20 tables, finding the right one is slower in the on-object flow than in the old data pane. The old pane is still available, you just have to know to open it.

Print/PDF preview behaviour hasn't fully caught up. The on-object overlay sometimes appears in PDF exports if you're not careful with how you trigger the export. We've had a couple of cases where a manager's email PDF had the action bar visible above a chart. Not catastrophic, just slightly embarrassing.

Where this lands

Microsoft has been chipping away at the Power BI authoring experience for years and most of the changes have been minor. On-object interaction is one of the few that genuinely changes how the day-to-day work feels. After getting past the muscle memory hurdle, I'm faster, and the analysts we've trained are getting to competence faster.

It's not perfect. The action bar positioning, the multi-select gaps, and the slower power-user experience are real. But the average builder will produce better reports faster, which is what matters.

If you want help with Power BI standardisation, training a team to make the most of the new authoring features, or just getting a stalled BI program back on track, we run Power BI consulting engagements and broader AI-driven BI work across Australia. Happy to chat if any of that lines up.

Reference: Use on-object interaction in Power BI - Microsoft Learn