I create a custom list in Sharepoint (modern list interface) and I add one column - choice field with multiple selections allowed. This shows as a dropdown in regular sharepoint list item edit mode.
I elect to create a new powerapp. The list is imported. The choice field isn't anywhere. It's not imported and I can't seem to reference it with "thisItem.fieldname"
I know choice fields are supported if they only allow one entry because I've tried. I just don't know if multiple entries are supported - or am I totally doing something wrong?
A Choice column in SharePoint Online list should be supported in PowerApps. I had a SharePoint Online list(Modern list interface) with a Choice column. The Choice column has three items. Then I create an App from the list in the browser. I can select choice items from the Drop down control and save it to data source. Below is a screenshot of the choice drop down control in my App.
Do you create an App from the SharePoint Online list in the browser? Do you have other columns in your list? Are these columns shown properly in the App?
Do you have PowerApps studio? Please try to create an App from data with SharePoint Online list to see if it works.
It's the 'multiple selections' allowed that doesn't work. A bit more googling and I found that it isn't supported.
Yeah, a choice with a single selection works, but multiple selections - both in the choice field and the people lookup is still not supported.
Ha ha. and I see you provided that same link in response to my other question. So we're circling around the same missing features. Thanks for your help MabelMao!
I am facing the same problem.
I created a PowerApp from scratch and added a SharePoint list as a data source.
This SP-List contains a column with choice fields.
The values of the choice fields are not shown in the dropdown.
Is this still worked on?
Appears to still not be fixed in the latest version - seems if you create app from scratch you cant link to a choice column in a SP list, but works if you create directly from a list, Which is no real use to me, when the main data source is from eleswhere. a backward way of creating things, and dont want all the default junk screens it creates.