Write multi-select combo box to SharePoint List column with data type choice (multiselect)

[finguin]

Hello, I've already done a whole lot of digging through various ressource but can't find a solution to my problem. 

Let's say I've got two columns in a SharePoint List:
1) Column A, data type: text

2) Column B, data type: choice, multiselect, three choices

I also have a Power Apps app, with two field:

1) Field A, text input

2) Field B, combo box, multiselect, three choices

The select values for field B are provided by a collection called "ColB" which is based on a separate SP-List. This is due to the app being multilingual which is not possible with basic SP-List choice columns. 

Now, is it possible to not only write the values from the combo box to column B but also update the record (column A and column B)? 

So far I've tried this:

ForAll(DataCardValue20.SelectedItems, Collect(ColB, {Id:ThisRecord.ID, Value: ThisRecord.field_3}));


Patch (DataSource, LookUp(DataSource, ID="111111"),
{
Column A: DataCardValue1_1.Text,
Column B: ColB
}
);

ClearCollect(ColB, Blank());

Unfortunately, this worked only partially. No issues with column A but column B seems to be a bit stubborn. Running the patch does indeed write the selected values field B into column B but only until I reopen the record to update Field B. If I click on field B it at first looks like that values are selected but then they are not:

If I now submit the form again, column B shows no values because after reopening the record no values are actually selected anymore. I guess it is probably due to column B being a choice column and the app is trying to store values from a collection into this column which is kind of a mismatch. 

Any input is highly appreciated! 

Cheers

Finn

[Talha_Dar]

You can also refer to this thread, as the same problem has been solved there.

https://powerusers.microsoft.com/t5/Building-Power-Apps/Combobox-parent-default-not-save-value-if-no... 

If you found my answer helpful, please consider giving it a thumbs-up or a like. Your feedback is greatly appreciated!

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[finguin]

Hi, unfortunately this does not solve my issue. It also looks like that in the example you liked the user is using a lookup which I don't. 

Or I am just not able to transfer the proposed solution to my setup....

[Talha_Dar]

Hi @finguin,

Try adding the following in "defualtSelectedItem" Property of your combo box.

Coalesce(
    Parent.Default,
    LookUp(listName, ID = ThisItem.ID).comboboxColumnName
)

If you found my answer helpful, please consider giving it a thumbs-up or a like. Your feedback is greatly appreciated!

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[finguin]

Does not really change anything. 

DSI of the combo box:

Combo box when editing the data set:

Though "Fossile Brennstoffe" appears to be selected, it is in fact not. If I wanted I could select it a second time:

OnSelect properties of the submit button:

I am sorry that this thing here is still ongoing 😕

Edit: I think this screenshot shows what is going on:

Even though two items look like they were selected, they arent. 
"DataCardValue20.SelectedItems returns an empty table...

[subsguts]

If you still have this problem, the reason is that what you have in your DefaultSelectedItems property is not matching what is in the Items property of the combo.  Most likely your combo box is populate with a field in the Items property and your DefaultSelectedItems is using Value and so it can't find it in the Combo Box to select it because the fields don't match.

I solved this by using the RenameColumns function in the Items property to make it populate the combo with a "Value" field instead of the original column name from the source.  This fixed the problem for me.

Again, if you are still wanting to solve this let me know as I've spent a number of days on this.

I can provide more details and a solution, but I assume you already figured a work-around by now?