Hi,
I came across an issue with list dropdown control values in edit form of power apps. It is not showing actual values available in dropdown column of sharepoint list in power apps edit form. please refer the below screen shots for the issue.
values given in list for dropdown field.
Values showing in Power Apps edit form for the same dropd down field.
Values saving in List after submitting the form, (above screenshot 3).
Kindly Reply as soon as possible.
Solved! Go to Solution.
The dropdown data control defaults to @odata.type to change this click the elipsis button and change the value to Value, you can then surface your choices as intended.
Just found this, this thread explains this a little better: https://powerusers.microsoft.com/t5/PowerApps-Forum/Choice-field-fails/m-p/9749#M4321
Hi saicharan,
If you user another SharePoint list that contains dropdown columns as data source, will the issue remains?
Mona Li
Hi monali,
Issue remains the same if we connect to another sharepoint list.
Not sure if directly related. Using the template to create 'Budget Tracker - tablet' app the dropdown in the edit screen shows blank lines and does not work. Seen dropdown not working in another sample, can't remember which. All created in last couple of days with GA release.
Update: This and other similar problems (with chart) only happen when running from PowerApps studio. If in design mode I select the screens and click on the controls (dropdown and chart etc.) then run, they work. This issue is in design/run and easy to reproduce with standard budget tracker template. Probably not related to the Sharepoint list problem, sorry!
The dropdown data control defaults to @odata.type to change this click the elipsis button and change the value to Value, you can then surface your choices as intended.
Just found this, this thread explains this a little better: https://powerusers.microsoft.com/t5/PowerApps-Forum/Choice-field-fails/m-p/9749#M4321
This is exactly the correct answer. I had the exact same problem
This workaround should no longer be needed. With the latest version of PowerApps, this should happen automatically.
Thanks
Murali
This workaround is still valid for Dynamics 365, however. I believe it works with sharepoint but not in CRM Dynamics 365.
Hi Saifmsk,
Correct, the work around is no longer needed for SharePoint.
Thank you for sharing about Dynamics 365.
That shouldn't be the case. Let me look into this and see what we can do about Dynamics 365. Thanks for sharing this info.
Thanks
Murali
User | Count |
---|---|
254 | |
106 | |
95 | |
50 | |
39 |