Patch multiple new records based on ComboBox with multiple selection

[Anonymous]

Hi, I'm pretty sure I'm missing something really simple here; I've checked other similar posts and tried different things but I'm obviously missing something fairly obvious!

ForAll(
    cboMarket.SelectedItems.Title,
    Patch(
        StoryDataGate1,
        Defaults(StoryDataGate1),
        {
            Title: txtDescription.Text,
            CustomerArea: cboMarket.Selected.Title,
            StoryType: cboType.Selected.Title
        }
    )
)

is my current code. It patches, but only adds one record and always the most recently selected item from cboMarket. I need this to post multiple rows if there are multiples selected in cboMarket.

Not sure if it matters, but there are many other columns that need to be patched; I've reduced the code for simplicity as all the others are single selections.

[WarrenBelz]

Hi @Anonymous ,

Try this

ForAll(
    cboMarket.SelectedItems As aMarket,
    Patch(
        StoryDataGate1,
        Defaults(StoryDataGate1),
        {
            Title: aMarket.Title,
            CustomerArea: aMarket.CustomerArea,
            StoryType: aMarket.StoryType
        }
    )
)

I am guessing a bit here, but have assumed that you are wanting to add the related fields from the Combo Box selections to the same fields in your list?

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[Anonymous]

Thanks @WarrenBelz,

So, for a fuller picture, the end screen will be multiple combos and text fields for a user to enter, the one combo, cboMarket has the opportunity to select multiple items. I want to add a new record for each selection in cboMarket, duplicating all other values to the other fields ... if that makes sense?

Struggling to get this to work, any idea? aMarket isn't finding CustomerAreas, nor many of the other fields in the table (I tried submitting with the errors and that failed):

[WarrenBelz]

@Anonymous ,

The As Statement is only for disambiguation - if the field names (gallery and data source) are different, you do not need it. I am not sure what field picker you have there, but if the field exists in the Schema of cboMarket (I assume this is a combo box), then you can refer to it with aMarket.FieldName.

What are the Items of cboMarket?

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[Anonymous]

Thanks @WarrenBelz, the use of As is new to me ... if that wasn't painfully obvious 🙂

cboMarket is indeed a combobox, with the items 

Sort(colMarkets,Title)

 which in turn is a collection made up from the OnVisible of the screen, basically looking at a very small SharePoint list (CustomerAreas) that are labelled in that list as Active:

ClearCollect(colMarkets,Filter(CustomerAreas,Status.Value="Active"));

it's unlikely that the list will ever get much larger than 10 records. It's the list of CustomerAreas that's being picked up by aMarket by the looks of it, and needs to be the intended list StoryDataGate1.

[WarrenBelz]

@Anonymous ,

Disambiguation has nothing to do with Delegation (I assume you were referring to the 10 records).

It is when your source and target fields have the same name - you can fix this with either an As statement (as per my post), a RenameColumns in the source or a [@Listname] disambiguation statement (which I have found not reliable).

colMarkets should contain all the fields in CustomerAreas (I notice you are patching to CustomerArea - is this a mistype or do you have two lists?

If you have two lists, then that is your problem is the field you want may not be available.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[Anonymous]

Ah, OK, that all makes sense @WarrenBelz. Yes, colMarkets does contain all the fields in CustomerAreas; however CustomerArea is the field in StoryDataGate1.

The list colMarkets is to restrict the items to the be patched to the main list of StoryDataGate1. Is this what's messing it up? The field CustomerArea in StoryDataGate1 is a single line of text field, so in my human logic it shouldn't matter where cboMarket gets it's items from as it does matter (if I understand correctly), is there a workaround that you know of?

[WarrenBelz · Accepted solution]

@Anonymous ,

Your logic is correct - it does not matter where you are getting the value from, but it does have to match the destination type (or you need some data shaping).

So looking at the selection side out of the combo box, as you have not restricted the fields in the collection for the combo box, all fields in the record selected are available to you. So for instance if you selected cboMarket.Title in the combo box, then you can also refer to (if this is a field in the record) cbMarket.Selected.StoryType.

When the ForAll statement loops though the SelectedItems of the Combo Box and you have used the As statement (aMarket), you simply refer to it as aMarket.StoryType.

Now if you also have StoryType as a field in the destination and it is a single line of Text, the Patch is

StoryType:aMarket.StoryType

If you leave out the aMarket, it becomes potentially ambiguous to Power Apps.

If StoryType is a Choice field, you need this

StoryType:{Value:aMarket.StoryType}

 Does that assist your logic in solving this?

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[Anonymous]

Awesome! Thanks @WarrenBelz you've helped me make sense of that, and is now (hallelujah!) working. A further complication was that in the SharePoint list CustomerAreas, the 'Title' field was renamed to CustomerArea, so aMarket.CustomerArea needs to be aMarket.Title. I must have been doing something odd following your first suggestion, as I tried Title. But! It's working now and I understand it ... finally! Thank you so much!