Today, when I opened up my powerapps app, I'm presented with a ton of red x's. It appears to save and publish fine, but any ideas whats going on?
Solved! Go to Solution.
I know they can be ignored but when you also train people on using the tool, it's difficult to say "please ignore" when sometimes they might have a true error. This needs to be resolved by Microsoft.
May 2021 and the issue is still unresolved!
Same issue with me! 28 Choice fields to be resolved every time I try to edit the app.
Been having this issue for years. Really not a problem. When published with the red x'es it will still work fine. It just shows that you have a data source issue, although there isnt really an issue.
And again - it is a runtime error caused by the load of the designer. It is not an error in your app! It's not going to get a lot of "fix" attention because it is not an actual issue, just an annoyance.
Another app builder here with the same issue. Open the app for editing and I get the errors (red and white X, red squiggly lines in the function/formula box under the data source, and the "data source supplied to the function is invalid" message in Details). Resolves when I clear and re-add my data source.
Love PowerApps, and I understand it's only an annoyance. But still needs resolved (IMHO), if only because it messes with your head. You end up spending a lot of time second-guessing yourself, and trying to distinguish what's a real error and what's a "false positive."
I think the issues of red x's were resolved. Thanks a lot!
It is true that it is just an annoyance during app building but it is breaking my apps in my circumstance. I am using ALM by using a solution in multiple environments. The app works fine in the Dev, unmanaged, environment. When I export and import into the managed, Test, environment, all of those combo box choices functions are broken and I get errors in the app and no dropdowns work. Editing the app in the managed solution to "fix" is obviously not the way to go.
So this is a severe bug in this case. I am unable to roll out the ALM environment structure due to this issue and unsure how to proceed as I can't find a workaround. Anyone aware of anything or is there a planned bug fix?