I've been having the same issue too. I created a post about this, which appears to have dissapeared. Microsoft needs to look at this as it's a re-occuring issue.
Have got the same issue, have an App that has not had any changes and the Dropdown stopped working for no reason.
Have tried all of the above mentioned actions to try and none of them have resolved the problem.
When are Microsoft going to have a look at this issue.
We experiencing this frequently. Forms that have been working will just suddenly stop displaying drop down options or the person fields liked to our AD will not populate once the user types in 3 or more letters. The only way we have been able to get the form to work again is to open it in PowerApps, delete all affected data cards, then refresh the data source and then save and publish, then reopen the form in PowerApps, add back the data cards, and save/publish.
While this fixes the form, it doesn't prevent this from happening again and therefore is not an acceptable solution. The most frustrating part is that the data cards often have formulas that we need to re-add once the cards are added back to the form. Sometimes these are quite complex and take some time to recreate.
There's no warning/alert when this happens so we have to wait until a colleague tells us the form isn't working. If they need to use the form urgently, they can't, and so we have to resort to paper forms until we have a chance to fix and test the form.
@Henryed07 @JohannaM @Axford_Clare We have recently committed a fix for a timing issue where ComboBox controls that are searchable can be unhooked from their data when the dependent data source is refreshed (or removed and added again).
I'll re-post a mitigation that is currently recommended from this post: https://powerusers.microsoft.com/t5/Building-PowerApps-Formerly/Sudden-appearance-of-red-x-s/m-p/371...
As we understand it, the issue may occur sometimes when the data source that a ComboBox control is bound to is either (a) refreshed, or (b) removed and then added again. The current advised mitigation that has seen success with customers is to perform the following actions after refreshing or removing/adding a data source:
This should allow the ComboBox controls to be correctly reconfigured to the correct values.
Also, if your ComboBox control contains only a small number of values, it is advised to disable IsSearchable since (a) this incurs a slight overhead when enabled, and (b) the issue of empty values only occurs when IsSearchable=true.
FYI--the fix is expected to be deployed to all production regions the week of October 21.
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020
The largest Power BI, Power Platform, and Data conference in New Zealand