EDIT: Please, if you're only reading/posting here because you want older PowerApps versions, please open your own or use a different thread.
I still have gotten nothing helpful back on my original post:
Please be so kind as to read my full post before responding.
Thank you for your consideration.
I have reported my issue already previously in the forums
and have already submitted a ticket
but, I have so far not yet received anything useful to fix my issue.
Thus, I am re-posting again to extend the reach of my call for help.
I only have one (but the most complex and important one) PowerApp that is affected.
I had/have one quite complex PowerApp that I have started working on last November.
It contains, among other things, 13 MultiSelect Option fields in Dynamics and a workaround for the ComboBox in PowerApps using Checkboxes since my bosses didn't like the whole-screen-filling-irritating-x-in-corner-look of the ComboBox (when pulled down) in the Android App.
That App worked fine until April.
Then I had to switch on the new CDS/OptionSet features for various reasons
This naturally broke all existing MultiSelect OptionSet related properties, and introduced (in a previously working app with 0 errors) ~1000 (mostly syntax) errors.
Working through the last month, I had managed to fix most of these
but now (passing through several PowerApps versions in the meanwhile) I am stuck at a state where PowerApps Studio effectively prohibits me from continuing my work.
The user interface seems responsive.
For all intents and purposes I have apparently wasted my time since the switch to new CDS features since I can't currently finish this PowerApp into a workable state.
Please do comment if you have experienced a similar issue.
If you do actually work or know someone who works in the actual PowerApps team, please do help me escalate my issue.
The support staff from Mindtree Limited have not been able to help me yet.
App ID: c106ea27-99b0-41e6-818a-190467867ecf
Excerpt of nonworking sessions:
Session ID: 65f7c777-468a-4823-9a0e-06789dfea55f
Session ID: c20946ac-7b2a-4822-a588-105a9bac62ac
Session ID: 487e9c6c-a071-411a-b9d1-fed42a310764
This only works for initial load. Seemingly the app checker runs whenever it wants during development which causes much confusion and delays.
We either need to understand what invokes the app checker or ways to defer it. Additionally, it would be lovely to be able to get an ETA for completion. I have been sitting on a checking time period of well over 25 minutes now for an app I was in mid development. I have no idea when/if it will finish and at some point I need to make the decision to just quit and start over again. Probably a half hour-hour worth of lost work.
Hi - did anyone else have any ideas about this? I have the same issue just reoccurred and no matter what I do I cannot get the app back to an editable state (exporting, restoring old version, etc). It is bizarre that this is happening with restored versions from months ago, long before this error every occurred - leads me to believe this must be something to do with a changed authoring version or something? (and no, changing the authoring version doesn't fix the issue because the app is left in a state where you cant change the authoring version!)
I had this issue a few months ago and raised a ticket with MS - after a couple of days they were still not able to resolve. I stumbled upon a solution through trial and error which was to export the app, then import it but to a different tenancy. Save it, then export and re-import it back into our production tenancy. That "unlocked" whatever was causing the loop or corruption and I was able to continue.
However, this time, that "workaround" isn't working and I am left with a broken app!
Anyone with any thoughts?
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.