Error adding multi-select choice field to customized form

[lalitm]

I have a choice field in a list that I built a customized form for. I updated the field to allow multiple selection. Now, when I edit the app and add that field to my form, it adds the datacard, but shows an error right away ("Expected Record Value") and the combo box does not allow multi-selection (the multi-select property for the combo box shows off, and it's locked). I tried to refresh the list data connection to no effect. Does the editor not support multi-select choice fields? Do I need manually update the code to allow multi-selection?

[FabianAckeret · Accepted solution]

Hi @lalitm 

Was your dropdown initially created without multivalue when you created your form based on a list? If so, Power Apps can't handle these updates very well. You can try to replace the dropdown with a combobox. Comboboxes are searchable multivalue dropdowns.

If possible, I'd create a new column with a new name (to replace the old one) - this time with multivalue enabled before you add it to your app. 

If you can't do that, simply create a dummy multivalue dropdown field, add it to Power Apps and compare each property from your Combobox AS WELL as your Datacard with the Combobox/Datacard that isn't working (pay special attention to the following properties: Items, Default, DefaultSelectedItems, SelectMultiple). Mostly, it's really something that got stuck there from your inital non-mulitvalue dropdown.

After that, you can delete that dummy dropdown again.

To answer your last question: The editor does support multi-select choice fields.

---

Please click Accept as Solution if my post answered your question. Like my answer? Consider giving it a Thumbs Up. Others seeking the same answers will be happy you did.

[lalitm]

Yes, I did change my column part way through building the app and you're correct that PowerApps does not handle updates like this very well and seems to cache all kinds of odd things. I was going to delete and recreate the column, but figured I'd try once more after starting my session fresh today and what do you know - it works today. Thanks for confirming that multi-selection is supported, I would have gone down a rabbi hole otherwise yesterday!

[rohitsbots]

After you change a existing field in sharepoint list to Multi-Select powerapps needs sometime to digest the change. No matter how much you refresh the datasource in your app it doesn't work. I faced this issue in customised form in a sharepoint list and for me the best solution has always been "Wait for 15-30 minutes" then reopen everything and then remove the existing cards and re-add them. It works like a charm!

[JoeFox79]

Just to add weight to the suggestion that patience is key here. I ran into this problem and, as I'm sure you all did, began searching for solutions and ending up here. First, I just want to explain what I did to encounter the error:

1. Modified an existing SharePoint choice column from drop-down to checkbox (multi-select)

2. Edited the Power App on which a card representing this column is within an Edit form component

3. Witnessed the error 'Expected Record Value'.

This is what worked for me:

1. Refreshed the data source (error still occurring)

2. Added the card again i.e., the card representing the now multi-select SharePoint column (error occurring on both cards - the original one and the newly added one)

3. Closed the app (by just clicking 'Back' and not saving.

4. Left my desk, made a cup of tea, drank the tea (probably about 20 mins)

5. Opened the app and added the card again (error now only occurring on original card)

6. Set all the properties of the new card accordingly and moved it to where the original card sits in the form

7. Deleted the original card

8. Saved app

I have no idea if 20 minutes was too long to wait, nor whether steps 4 and 5 were required, but at least I had a nice little break and a decent cup of tea. I guess the key here is that sometimes having a little patience, however frustrating, is important. 

[JoeFox79]

Just to add to my post, encountered the same problem again today and this time, I refreshed the data, closed the app, reopened the app, and from there was able to add the card again with no errors showing in the new card. 

It does appear that the original card is just wrecked and needs to be deleted, but I can deal with that as long as re-adding the card solves the problem (and that there aren't 100 instances of this on the app!)