Hit Reply to tell us what you think about the new On-Object Interaction feature so we can continue to improve.
-Power BI team
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.
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."
The thing is @RosieL it's baffling as to why MSFT keeps putting resources into this feature when the userbase is screaming out for (1) new, better and more functional visuals, (2) speed and efficency improvements, (3) more modelling and ETL features..... it's disheartening.
100%. I have seen almost none of that in the last 3+ years that I have been using Power BI. All of those were my biggest gripes about moving to Power BI - those issues can only have gotten worse.
Ease of developing simple dashboards by new users was arguably Power BI's outstanding feature - this UI change will take even that away!
It is a terrible feature, because it is not feature complete. For example, how to add conditional formatting to measures?
And sometimes these On-Object buttons are available, sometimes not.
The classic way worked fine for many years, these new feature is like an alpha version. Please focus energy on more important features.
Previews are fine, if they add something. But previews are not good, if you remove existing features and functionality.
Dear Microsoft - Please, please stop focusing on things no one wants or likes instead of addressing the requests by the people actually using the product!!!
As a UI designer myself, I know better than to think that MS is going to maintain the current UI and the new UI indefinitely. It's disappointing that someone at MS has blindly decided on a path that is clearly unwanted by the vast majority of users. I'm sure you feel like you're incorporating user feedback, but only inasmuch as you're incrementally improving a fundamentally bad design decision. You're breaking the cardinal rule of "if it ain't broke, don't fix it". Everything in the current UI works, is intuitive, and efficient, but for some reason MS is charging forward with its own ungrounded UI, apparently for its own entertainment, forcing existing users to entriely re-learn how to use PBI and making it harder for new users to learn it. I've been using PBI for several years and have typically championed the ongoing developments, but development for development's sake is a really worrying precedent that gives me concern that I can't trust PBI as a long-term solution.
Agreed. Seems MS is more interested in changing the UI for appearances sake (a.k.a. "new and improved") rather than addressing less flashy, but more desired features requested by their users. They see all this resistance and still press on with unwanted changes.
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.
130+ sessions, 130+ speakers, Product managers, MVPs, and experts. All about Power BI and Fabric. Attend online or watch the recordings.