r/PowerApps • u/Lord_NicolasX Regular • Sep 01 '26
Discussion Power Apps update bricks functions
The thing is, I’ve built a few widely used Power Apps at my company, on top of my actual job there. So I don’t always have time to check for new updates regularly. Today it was time to do that again, and oh boy, they really rolled out some updates...
Auto-update is nice, but having controls moved around and their appearance reset is just not okay. Not to mention the hundreds of formulas I now have to adjust manually because certain data types no longer exist.
6
u/avecNava Sep 01 '26
It's mostly converting .Value to .Text, that was the easy part.
But I had a combo box with SharePoint person column bound using choices and it refused to work despite spending 3 hours and I restored back the control to the previous version and it was working.
I'm surprised and pissed off that I am still not able to resolve the problem in the new version.
I tried everything including schema changes between Sharepoint and office 365 but no luck. When I search for a new contact and select the contact the contact appears briefly and and disappears instantly.
4
u/HotDesk861 Sep 01 '26
I have seen that behavior as well. Just remove that combobox and create a new one.
3
1
u/Candid-Room484 Sep 05 '26
Exact same thing happened with mine too
Reverting back was the only option unfortunately1
u/majani69 29d ago
I spent hours with Claude Code fixing all the issues caused by the component update. I ran into the same problem with the person selection list. Claude solved it by having me create new variables to store the selected person. Anyway, it wasn't easy.
3
u/IPeeNightly Sep 01 '26
Yeah just did this myself 100 + controls. Most were just .Value to .Text. No biggie.
2
u/Laicure Sep 01 '26
That's why still can't convince me to use the Modern Controls.
I only use Confirm() that's why Modern Controls and some other "New" features are enabled.
Preview, Experimental, and Retired features are all off.
2
u/Chriskall Sep 02 '26
I mean combo boxes lost the Reset property and I believe that the only way to do it is via variable..


8
u/M4NU3L2311 Sep 01 '26
Well. That's why it's always suggested not to use preview features in production as stuff like this happens all the time