@Anonymous, @v-micsh-msft ---
So, I just discovered that the PA team had already fixed this bug. I know that I should be happy about this but no. I've waited a couple of months for the fix until I just gave up and tried to think of another way for it to work with PA. (I wasn't fun.) Now, it wasn't even mentioned in the update notes. Heck, I wasn't even notified that it was fixed when I reported this bug in the community dedicated for PA. This is one of the things I hate most about PowerApps right now. All the silent updates. All the silent changes. I am just so glad to be rid of PA in the next few weeks.
Just in case the Support Team and/or Dev Team is listening (which I doubt, given my experiences), I really hope this changes in the future. AND DON'T MAKE ME PUT THIS IN THE IDEAS SECTION. Why do I have to suggest to you what should have been done in the first place? PA is not for just end-users. You're working with app creators now, who should be aware of the subtle changes that are done in the background, just so that they know that whatever workaround they put up so that their apps will work will still work post-update. And if it doesn't, let them know what changed so they know where to start in fixing their apps.
And for whoever may be mad at me for ranting in this forum, I just hope that your PA experience is better than mine. Good luck.
