Come to my attention that the behavior of dropdowns changed a bit based on its contents. Not sure when this happened, as my user was not sure when the error started.
I had a dropdown which its items (timeslots) were defined in an array like ["","07:30","08:00","08:30","09:00"]
The dropdown looked like this
After the user reported the bug, I checked and indeed the dropdown had changed to this (again, 100% sure nobody touched this app last couple of months)
Seems that the first item of the array, being empty/null, causes the weird behavior. Solution is either move the empty/null to the end of the array, ["07:30","08:00","08:30","09:00",""] or use a blank instead of an empty/null [" ","07:30","08:00","08:30","09:00"]. In either case User will need to select the last item when they need to blank the dropdown, or the app needs adjustment to deal with a blank instead of the empty (samples below).
Interesting issue! I was able to replicate it using the new "Dropdown (preview)" control. The old "Drop Down" worked ok.
I was able to fix it by setting the "Fields" property of the "Dropdown (preview)"
Add the "Value" field
This works for me, even with the blank as the first item in the items collection. If this helped you, please click "Does this answer your question" and give it a like to help others in the community (+ close the ticket)!
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
2
Share
Report
All responses (
Answers (
