Patch People field that allows multiple values

[bregan507]

I am trying to Patch a SharePoint People field that allows multiple values. I have been able to patch a SharePoint People column as long as it contains one value...but if the People column allows multiple values, my patch statement only gets the first value and does not work properly. I don't want to use a form and would really prefer Patch, but I'm stuck on this. My People values are coming from a combo-box in which the user inputs multiple people...anywhere from 1 to 6 people...so the Patch statement can't be hardcoded and must be able to read the input from the user via the combo box. 

[RandyHayes]

@bregan507 

You will need to supply a table of persons to the column during patch.

Please have a look at this post, it should explain pretty much what you are trying to do.

I hope this is helpful for you.

[bregan507]

Thank you...that worked. But I'm having a weird thing happen now...
If I put in person1, person2 into the combo box and click submit, the patch works now. All is well. When I go back to the same record, and add another name, it updates the record but deletes person1, person2 out of the SharePoint list. In other words, When I go to the record to edit it and input person1, person2 into an empty field and click submit, it works. When I then go back to the same record, and modify that combo box (that already has values) to read: person1, person2, person3 and click submit, it updates the record...but if I go back to that same record now, it shows person3 as the only entry. Any ideas on why that is happening? 

[RandyHayes]

@bregan507 

Yes, adding in additional people does not "add" them, it replaces the list.

If you want to add people, then you would need to supply in your patch, the entire table of people (the existing and the added).

If you have a hard time working that out, then let me know what the DefaultSelectedItems property of your ComboBox is and I can help work it out with you.

[bregan507]

You're awesome...thank you. I'm new to PowerApps (this is my first app). I've been working in InfoPath for years, and trying to figure out PowerApps...it's different. I very much appreciate you helping me...thank you again. 

On my cboReviewers (this will write to the Multiple Person field in SharePoint) the DefaultSelectedItems: varRecord.Reviewer (When the user click the record in the gallary on another screen, the OnSelect is: Set(varRecord,ThisItem);Navigate(ScreenEdit,Fade)

[bregan507]

My patch statement is something like this: (I can't paste it exactly because I can't login to this forum from my work computer so I'm typing it in manually here)
Patch(
    cqdata,
    varRecord,
    {
        Reviewer: 
            ForAll(cboReviewer.SelectedItems, 
            {
                '@odata.type':...
                Claims: Mail, 
                Department: "", 
                Email: Mail, 
                JobTitle: "", 
                Picture: "",
            })
     })

[RandyHayes]

@bregan507 

No worries.  I know going from InfoPath to PowerApps is like moving from Earth to Mars...eventually you learn to breathe the air 😉

So, the first thing to note about your desired solution is that you will NOT be able to remove people from the Person column in your list as you are only going to be appending to the list each time.

So, here would be where I'd start - take the formula for building the multi-Person column from what was suggested before and then combine with the selected items.  

Here is how that would look:

ForAll(
    Filter(Split(Concat(cboReviewers.SelectedItems, Email & ";") & Concat(varRecord.Reviewer, Email & ";"), ";"), !IsBlank(Result)),
        {
        '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
        Claims: Result,
        Department: "",
        DisplayName: Result,
        Email: Result, 
        JobTitle: ".",
        Picture: "."
        }
    )

This will turn the selected items in the combo and the current record items into a string (with the Concat), then it splits it and uses that in the ForAll (Filtered to remove blanks).  You will have duplicates most likely, but SharePoint will sort that out.

See how that goes for you.

[bregan507]

Thank you again for trying to help me...this seems like a lot of frustration. This seemed to work then it didn't work - it's weird - I put in the code, and it looks fine. I run it and it doesn't update. I go back to the code and now there are red squiggly lines everywhere and I didn't change the code. Earlier, I used the code and it updated the field but wouldn't update a blank value. It's like the code works sometime, and shows errors other times. I've scraped all my changes and reinput your code now nothing is updating and the red squiggly lines disappear if I add a space somewhere in the code or remove the "requestor" code. My goal is to get this to work like it did in InfoPath...where the user can add 1, multiple or 0 items in the "Reviewer" field.  Thank you again for your time helping me. 

[RandyHayes]

@bregan507 

If you are actually trying to submit back an Empty record, you will need to make sure that you have the "Formula level error management" option turned on in your Advanced app settings.  Otherwise it will not work.

What is your Formula now showing?  What are the red-squiggly lines telling you the error is? (hover over them to get the error)

[bregan507]

It's weird...the same code that was giving me red lines just started working. I closed and re-opened the window and that seemed to help. The patch is now working but I need one more thing...If the user wants to remove someone, this is not removing. Thank you.