cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Multi-Select Person Field, How to set the DefaultSelectedItems to what was stored in the SharePoint Field

I know this has been discussed multiple times, but there is always some wrinkle on it.  I'm hoping what I need is very simple for someone to answer and that I'm just missing it.

 

1.  I have a field called ListAllProvidersChoice in Sharepoint that is a Multi-Select Person field

2.  I have a combo box where one can select users from the O365.  It's Items property is set to:

Office365Users.SearchUserV2({searchTerm:Self.SearchText}).value

 

The combo box works.  The Patch works to store the selected people.

 

The problem:

 

I cannot get the DefaultSelectedItems populated with what is stored in the SharePoint Person field, which again holds multiple people searched and selected from the O365.

 

Appreciate the help.

1 ACCEPTED SOLUTION

Accepted Solutions

@subsguts .

One of the (many) reasons I do not use complex field types is just this. The Items of the combo box need to be a Table containing all the elements of the field type (in this case you need DisplayName and Mail to be in there). Once you start changing the content, you risk not having one or more of these elements (Lookup fields are another prime example here) and then cannot write back to the field.

In the case of People, I have a list of the names which is saved to a Text field and then have another text field (which you can hide) defaulting to a lookup on the email and saving each time the name is added or changed. Everything is Delegable, you can Sort on it and write back with nothing more than the control content.

View solution in original post

11 REPLIES 11
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @subsguts ,

I just did an example here with the Items as you have them and the Data Card Update 

ForAll(
    ComboBoxName.SelectedItems As aSel,
    {
        '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
        Claims: "i:0#.f|membership|" & Lower(aSel.Mail),
        Department: "",
        DisplayName: aSel.DisplayName,
        Email: aSel.Mail,
        JobTitle: "",
        Picture: ""
    }
)

and the DefaultSelectedItems (in your case)

ThisItem.ListAllProvidersChoice

and it stored and displayed the items perfectly.

 

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.

Visit my blog Practical Power Apps

 

This didn't work for me.  It is giving me an error.  

To provide more information, below is what my combobox looks like.  Is called, "cmbListAllProviders"

subsguts_0-1669065495820.png

 

In addition, this field is on a fluid grid, and I use a Patch statement inside a Save button to Insert and/or Update the field in the Sharepoint List.

 

If I add the code you suggest to the "Update" property of the Card this combobox is on it gives me an error, saying, "Expected Record Value".  I put exactly what you have except I changed "ComboBoxName" to "cmbListAllProviders".

 

I don't know where to go from here.  I'm a bit confused as to why the Update property has to be used and why the DefaultSelectedItems can be set to what is stored in the Sharepoint Person field.

 

Appreciate you help as I've been wrestling with this for hours, read and watch tons of videos to no avail.

 

Thank you so much

I think I figured it out, with your help, it clicked when you said "ThisItem".  Since I get to my screen to the update of the record by selecting it in a gallery, I add the following to the DefaultSelectedItems

"BillAreaRequestGallery.Selected.ListAllProvidersChoice"

With BillAreaRequestGallery being where I select what record I'm working with.

 

This appears to work.  My only worry is making sure I don't need the change the the "Update" on the card?

 

Thanks again

While setting the DefaultSelectedItems to "BillAreaRequestGallery.Selected.ListAllProvidersChoice" works in bringing back the stored values.  It prevents the user from additional people using the O365 lookup.

So still not there yet, any help is greatly appreciated. 

Ok, I officially HATE combo boxes.  So, when I changed the default property, it also did 2 other changes, which I didn't make.

 

1.  It turned off "Searching", so I had to turn that back on

2.  It changed the secondary field, not the search field from Mail to JobTitle (so I changed this back)

 

I think the combobox has bugs in it, especially with Search because it flips that flag without any reason. 

 

@WarrenBelz , so I think that it's done except for understanding the Update property of the card and to ensure I don't need that.  Thanks for your help as sometimes just talking about a problem will bring my brain to a new place.

Hi @subsguts ,

The one way to test this (I would need to build a model to do this)  is to save something and see if it shows both in SharePoint and your Combo Box.

BTW I dislike (intensely) Person fields and any other complex type and simply do not use them. SharePoint is a data storage and Text, Number and Date fields have been totally adequate in everything I have written over the last 5 years.

Everything is being inserted (New Record) and bringing back what is stored correctly now for the Person Combo Box.  However, if I try to add an additional person and save it, using the same Patch syntax it gives me the following error and doesn't store the added names.  Any Ideas, why it can't find the mail? (I have a feeling it's because when I default select the items in the combo it isn't truly selecting them and getting all the properties of an O365 mail item, sorry don't know how to word this better).

 

subsguts_0-1669068794994.png

 

As always thank you for your time.

@subsguts .

One of the (many) reasons I do not use complex field types is just this. The Items of the combo box need to be a Table containing all the elements of the field type (in this case you need DisplayName and Mail to be in there). Once you start changing the content, you risk not having one or more of these elements (Lookup fields are another prime example here) and then cannot write back to the field.

In the case of People, I have a list of the names which is saved to a Text field and then have another text field (which you can hide) defaulting to a lookup on the email and saving each time the name is added or changed. Everything is Delegable, you can Sort on it and write back with nothing more than the control content.

After a lot MORE reading, I have FINALLY gotten this to work without a lot of additional gymnastics (code, work arounds, etc.).

 

First, when you populate the DefaultSelectedItems of the ComboBox referenced in this discussion it WILL NOT populate the Mail.  However, it will populate the DisplayName.   If you select the item using your mouse, from the drop down, it will populate all the fields, including Mail, but for some reason it doesn't do this when you pass it a Person structure in the DefaultSelectedItems (as described in the other threads of this discussion).  

 

Hopefully this makes sense.  The way to compensate for this on your Update Patch is by doing the following:

 

Here is the Patch for the Insert (pretty standard and works wonderfully):

 

ListAllProvidersChoice:
ForAll(cmbListAllProviders.SelectedItems,
{Claims:"i:0#.f|membership|" & Lower(Mail),
Department:"",
DisplayName: DisplayName,
Email: Mail,
JobTitle:"",
Picture:""
}),

 

Here is the Patch for the Update (which requires you to do it this way in order to get the Mail since it is not selected when you use the DefaultSelectedItems to populate the combo box with what was previously selected and stored in the Person SharePoint field-changes in bold😞

 

ListAllProvidersChoice:
ForAll(cmbListAllProviders.SelectedItems,
{Claims:"i:0#.f|membership|" & Lower(LookUp(Office365Users.SearchUserV2({searchTerm:ThisRecord.DisplayName}).value, DisplayName = ThisRecord.DisplayName).Mail),
Department:"",
DisplayName: ThisRecord.DisplayName,
Email: "",
JobTitle:"",
Picture:""
}),

 

Thanks again to @WarrenBelz for helping me get to a solution.  I'm hoping this will help others as this was a 4-5 hour puzzle 🙂 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,584)