Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Grow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.

Reply
RosieL
Power BI Team
Power BI Team

Share your thoughts on the new On-Object Interaction feature (preview)

Hit Reply to tell us what you think about the new On-Object Interaction feature so we can continue to improve.

For example:

  • What changes would you like to see?
  • If you turned off the preview switch, why?
  • Any suggestions for addititional settings or capabilities?

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:

  • Q: How can I open multiple panes at once?
    • A: You can CTRL + click or right click on the unselected pane you wish to open and choose "Open in new pane"
  • Q: Where did aggregations move to?
    • A: It's still on right click of a field, or you can use the new flyout aggregations dropdown while choosing or swapping a field.
  • Q: Where did drillthrough and tooltip page setup move to?
    • A: Drillthrough is now in the page settings of the format pane under Page Information > Page type > Drillthrough or Tooltip.
847 REPLIES 847

@foodd I had a very similar response, see that I was asked to wait for June and July, but August and September have also passed, and they are light years away from an interface that has advantages over the current one, I'm still optimistic, I hope they implement several new features in the current standard and that’s it.

Yeah none of this is surprising really... companies do what they want. As someone who used to be a customer, then an employee at Tableau, I can tell you that regardless of how they market their customer-centric focus, feature changes are about either A) making developers happy/lives easier or B) money. I am glad that there is a way to turn this off, for now - let's hope it does not become permanent. I have had so many problems with options disappearing in the pane switcher, and I find absolutely no benefit to the on-object interaction despite seeing others promote it as helpful in one way or another. 

I don't oppose change, but it needs to make sense and be well communicated to users. Why not have some sort of message when something like that comes out to all users, or a prompt when you open the software to let you know about the change and how to revert back to what you are familiar with? I just see so many ways to avoid this confusion... but alas, I'm not a software developer, just a meager data visualization consultant/analyst, so I suppose what I say doesn't really matter much 🙂

I agree with you.

Would you go back to Tableau?

Stat
Regular Visitor

Definitely not a fan. I've tried it a few times now & it just makes everything harder & less intuitive. Proper detachable, floating panes would be a much better option than making the panes fight for space with your report.

HasnainAk
Advocate I
Advocate I

I don't think this change is necessary because it won't add much value, and it will make me work harder to do the same thing. I also think the existing feature is mature enough, so changing it doesn't make sense to me. Instead of adding better features, product teams are just making these random changes to product that dont make sense to me.

This is a wretched change. It is as poorly thought out as the name of this preview feature. Please don't even consider turning this on. Another user accidentally turned on this preview feature and I had to troubleshoot with her how to turn it off. It was taking her much more time to develop visuals, because of this major change to the UI. ...and she just learned Power BI 6 months ago.

 

Why is it terrible? You cannot easily add data fields to your visuals. Here is what is required:

 

Steps in the normal UI to add data:

1. Click on visual to add to your report

2. Click on the checkbox to add field to visual or drag to the "Build visual" pane

 

Steps with the "On-object interaction" UI:

1. Click on the dropdown arrow to select a visual

2. Click the visual you want

3. Click on the visual

4. Click on "Add data and build your visual"

5. Click on "Customize pane switcher"

6. Click on "Data" to enable data

7. Click on the "Data" icon

8. Click on the checkbox to add field to visual or drag to the "Build visual" pane

 

...and if you go to another visual, you have to repeat steps 3, 4 and 8 every time. What a nightmare!

 

Do you see the problem here, Microsoft?

 

What I would like is if you combined "Format Visual"/"Visual" "Format Visual"/"General" and "Analytics" in the same pane. That never made sense to me. Instead, it looks like you jumbled visual, general and analytics even more. What a mess. I do think the current Power BI interface is clunky and that options are buried under too many menus - don't make the same mistake twice.

 

I don't normally provide feedback, but I wanted to get ahead of this horrible change to try to persuade Microsoft developers to avoid the barrage of negative feedback they will receive if they attempt to make this preview option the default UI.

 

I also hate that you added the "Desktop layout view" and "Mobile layout view" where the page navigation buttons used to start - was that really a big request? Why not put them on the bottom right for the few users who are switching between the two layouts often?

I agree

I've been saying the same thing over the past five months. MS seems intent on changing this for the sake of change, not to improve functionality. Members on this thread have shared many other functional improvements to the interface that have been desired for a long time. However, MS seems to be doubling down on making this unwanted change, regardell of the feedback provided.

I really hope that users and developers are heard, the change would only be welcome if it brought benefits, so far I haven't seen that, although I like some changes, such as being able to edit the header directly in the visual or collapsing the buildvisual, but these changes could be implemented in the current mode, then they would be improvements and not what is being proposed with many more clicks, greater space occupied, etc. I hope common sense at MS prevails.

Kdhosk
Regular Visitor

Hi. I like the new On-onject Interaction feature. A couple of suggestions;

-have Power BI save my pane preferences so I don't have to go to the View tab and re-add all the panes I want to use every time I open a PBI file

- allow the developer to increase/decease the width of the on-object pane (at least to a certain degree)

- make the pane icons "Drag and drop-able" to open new panes

Kdhosk, I respect your opinion, but although I liked several new features, they could be implemented in the current mode, excessive clicks and "bugs" do not allow us to use this new feature in production mode. So far you are the only one who has approved it, the vast majority are not very happy, and I include myself in the majority.

Good point, and that about sums it up.

LewisCoghlan
Advocate II
Advocate II

Hey All - maybe not the correct answer, but in response to everyone asking why they keep pushing time and resources into this feature despite the community showing zero interest is answered by viewing a demo for the future AI report builder for PowerBI/Fabric. 

 

My gut tells me that Microsoft are aggressively pushing towards a future where the development of reports is basically just providing a dataset and using natural language queries to get an AI to build your visualisations for you. From this perspective, On Object Interaction makes a lot of sense, as building a report will basically just be formatting and re-arranging, not actually building measures, adding data fields to visuals, or building out anything at all. 

 

I hope that this won't result in the old development interface being scrapped, because I am dubious that this approach will be able to effectivly replace ALL report building, but based on the demo I've seen I can definitely see that in the next few years we'll be able to use AI natural language query to build 80% of reports, and then only the more complex 20% will require actual development.

I'm not against the idea of On-Object Interactions if they are well designed and implemented. It's the way it's happening that's the issue. There seems to be massive pressure for it to happen. Maybe actually with the goal of replacing the majority of us developers with AI. You see the trend everywhere: you want to, but it doesn't yet work the way you want (fortunately for us) with AI.


Surely a mandatory requirement should be that a new feature is better than the existing implementation, that no functionality disappears, that operation becomes more intuitive and requires fewer clicks. These things are not given here: Functionality disappears, you need more clicks, it is less intuitive.

 

If you're going to force a feature like that into the product for whatever reason, then please make it an optional extra. Then we could turn it on and use it occasionally without being disturbed too much in our daily and usual work.

maybe I don't hang out in the right places, but it seems that it is just crickets from MSFT in response to the ovewhelming disappointment and negative feedback about on-object interaction.

If they are unable to articulate a compelling resaon for implementing it, what is their purpose?

I couldn't agree more. They pulled the same crazy , insane stunt in October '21 when they changed the DAX editor over to the current monstrosity and that time they literally did spring it on us without any prior warning or justification whatsoever and didn't even acknowedge that this change had been made. This drove most users serious about DAX, or frankly those that just wanted to be able to see the DAX that they were authoring over to Tabular Editor 3 , such ws the shody implementation. Now we are here again. Personally , I think the 'On object'  idea is for want of a better term,  "absolute crap". There is no justification to it and Microsoft need to 'Listen' to the user base and fall in line. It's a knock back , but it's better than a reduced user base and an abadoned product. 

100% Agree. Definitely not trying to indicate that I'm in support of the changes whatsoever - I think the on-object interaction is a terrible piece of functionality for the purpose of PowerBI as a tool that objectively makes the product worse to use. Microsoft is going about it's development and the communication of it's motivaitons in a truly appalling way that is causing anxiety amongst the user base as to the future of the product. 

However, in lieu of Microsoft actually sharing WHY they are pushing this "improvement" out (despite the communities recurring questions) I thought I'd try and give a plausible reason that may at least try and help explain and dispell some confusion.  

If AI can replace PBI, then it can also replace SQL, SSMS, but nothing happened to those. Also, I could not see the logic how turning a good, universally liked UI into a terrible one helps MS with anything. Surely MS can find other way without alienating its entire user base. 

I agree.

germo
Advocate IV
Advocate IV

When Power BI came out many years ago, I was skeptical at first because of many missing features. Then Power BI got better and better. In the meantime, I even prefer Power BI for tabular modeling. Not because it is easier, but because the overall concept of Power BI Services and Fabric convinced me. And that's been the case since Fabric came along. I even started recommending my customers to switch from SSAS instances to Power BI Services / Fabric.

And no sooner had Power BI / Fabric convinced me as an overall concept, than all of a sudden such a preview feature comes - like a hammer on my head. As if God wants to tell me: Keep your hands off Microsoft, don't get too dependent.

Instead of improving the product, important and proven functionality is removed. How can you use a feature like this for productive use of Power BI? How is one supposed to work seriously with the existing limitations? Especially since the description of the limitations is also incomplete, there is no indication that conditional formatting can no longer be created. By using this feature, there is even a risk of destroying existing reports.

My trust in the Power BI product management has suffered a lot due to this feature.

We know this phenomenon from many vendors who develop modern looking apps with missing features because they think they should keep up with the times: First with the parallel possibility to use the products classically and in the mobile app. Then one day the forced redirection from the mobile browser to the app takes place. With the result that normal work is only possible via a desktop, but no longer on the smartphone.

Is Power BI now also infected by this disease: Hip and Cool and Modern instead of Functional? Can we still trust the development of Power BI? Have I backed the wrong horse?

What if there are multiple Power BI developers in a company: are there administrative ways to prevent the use of certain preview features to prevent the accidental destruction of existing reports? Until this feature, it would never have occurred to me that users should be forcibly protected from features. There is definitely a clear warning missing here before activating the feature: "Existing reports can be accidentally destroyed. Many features are missing. Do not use this feature productively, only for testing."

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

Power BI Carousel June 2024

Power BI Monthly Update - June 2024

Check out the June 2024 Power BI update to learn about new features.

RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.