Hit Reply to tell us what you think about the new On-Object Interaction feature so we can continue to improve.
-Power BI team
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.
Another factor for Microsoft to consider, is that when a user responds to this thread, they automatically receive an email with every new comment. This means that every person who has commented here receives multiple emails every day showing not just negative, but increasingly hostile responses to this feature. People used to say "I'll never use this," and then "I won't use Power BI if this becomes the only way," to now "I'm going to stop using Power BI because I assume Microsoft is going to make this the only way." Because we are all subscribed to this thread, this overwhelmingly negative sentiment multiplies in the hearts and minds of the core user base. It is painful to watch this go on for months without Microsoft addressing how they will turn this around, what the long term plans are for this feature, and why Microsoft continues to invest in such a wildly unpopular feature.
My opinion is that this feature is being pushed too aggressively and with very poor testing. After multiple crashes early on, I haven't touched it. Things like managing panes is such a basic usability issue, that I don't think Microsoft is doing any significant testing before we see it. While this is ok for small features that are mostly polished, this change is too big and too rough still. It feels like we are alpha testing, not beta testing. The whole world should not be your alpha testers! We are on a monthly release cycle, so by the time we give you feedback, it takes months before the fixes come back to us. That isn't workable for such a large change. At the pace you are on, it will take years before this change is usable. And you are depleting your pool of testers when people turn it on and have to turn it off after 5 minutes of testing. Many have made up their minds on this change by now and won't touch it anymore. How are you going to get feedback then? You need a smaller, highly active test group of seasoned developers who want this feature and a weekly release schedule. Pull the preview until your alpha testers are happy.
Something needs to happen though. Continuing on as-is hurts the trust we place in the development team. This thread is a festering pool of negativity. If you don't address it somehow, I think you will see the sentiment toward Power BI continue to decline with your core users.
Well said, come on MS, what about some basic features that are still missing on visuals:
- Freeze panes on a table
- Drill through on a multi row card
- A better guage visual with multiple ranges
- The ability to fix the slicer type (as say between) when using 'Show values on selected field'
Just focus on the visuals, that's where you're falling behind the competition. You're relying on the easy transition from Excel to Power BI with people's existing license agreements, rather than genuinely trying to compete in the market space
The MS person who decided down this path has definitely NOT used PBI on a daily basis. Knowing how large corporation works, it is hardly a surprise, just profoundly SAD for the community.
There are many useful features the community asked for over years, very few got implemented. Instead, MS happily chose to waste 1 year of development time on something everyone hates, and no one asked for.
I completely agree, development time could be spent on improvements to the current one that would be welcome, and not on a new one that is totally hated by the majority of developers.
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.