I have created a simple sharepoint list with 3 columns, one of which is a Choice data type. As shown in the following image, it is not working. How can we troubleshoot this?
Thanks for reporting this. This is a known issue on our end and we are looking into fixing this soon.
You can do the following to workaround this issue:
1. Click on the card corresponding to RequestType and go to the Options pane
2. Click on the "..." and you sould see a customization pane
3. Change what Value1 is mapped to from "@odata.type" to "Value"
Thank you so much for providing this solution! Do you know if this will work for Managed Metadata?
Thank you so much for providing this solution! Do you know if we can get read-only managed metadata working within powerapps?
@Karthik to help with your question.
This workaround for Choice and Lookup fields should no longer be needed. PowerApps should automatically do the appropriate binding with the latest version
Thanks
Murali
I cannot seem to get any choice fields showing - I am using the DYnamics 365 data source and using an "allowed values" drop down control, but you cannot drop down the selector, and therefore cannot see any of the options.
Is there a way to use the Choice control to accomplish the same thing?
Is there an equivalent work around for Flow fields?
Perhaps there is an expression to convert the odata to values?
Old post, but this problem has been occurring frequently on my current forms often randomly when editing completely unrelated parts of the app. As there is no longer the option in the ellipses to attempt this workaround, I am at a loss. Often I can get it to fix its self by repeatedly refreshing the data source. There has to be a better option. Please help.
I am having the same issue. I have to keep refreshing my data source until all my dropdowns work. The way I worked around it was to directly input the sharepoint choices into the items option of the dropdowns.
@Turtlestein wrote:Old post, but this problem has been occurring frequently on my current forms often randomly when editing completely unrelated parts of the app. As there is no longer the option in the ellipses to attempt this workaround, I am at a loss. Often I can get it to fix its self by repeatedly refreshing the data source. There has to be a better option. Please help.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
199 | |
68 | |
46 | |
36 | |
25 |
User | Count |
---|---|
241 | |
108 | |
89 | |
87 | |
66 |