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

Filtered people picker - patching result to SharePoint list

My scenario:

List A (list with stored data from the form)

List B (lookup for Vendor and Manager fields)

 

I have a form connected to a SharePoint list (List A) with a people picker (Manager) that is filtered from another SharePoint list (List B) based on a selection from another combobox (Vendor).  When user selects a Vendor, the Manager field should display filtered values from List B.  I have managed to get the filtered results in the field, however I can't seem to get the values patched to the SharePoint list (List A).

 

Here is the formula I am using for Manager combobox where it correctly shows Emails for all the filtered results:

If(
    varViewProduct = false,
    Office365Users.SearchUserV2(
        {
            searchTerm: Trim(Self.SearchText), isSearchTermRequired: false,
            top: 10
        }
    ).value,

        ForAll(Filter(
            'List B',
            Vendor = cmbVendor.Selected.Value
        ).'Manager','Manager'.Email)
    )

 

When Patching the manager field in the OnSuccess property, Email is not recognized.  I've looked at the card and DisplayFields and SearchFields only allow ["Value"] and wont allow ["DisplayName","Email"].  I suspect it's the way I'm filtering the Manager combobox(?) but can't figure out the right recipe to get this to work.

Note:  user should also be able to enter another Manager that is not filtered, if desired, thus the If statement.

 

Any tips?  Thanks in advance!

2 ACCEPTED SOLUTIONS

Accepted Solutions
Amik
Super User
Super User

@StacyO - The Office 365 users table and the SharePoint AD table share totally different schemas. You're going to need to use a separate solution for that scenario by dynamically changing the same table based on the output of "varShowOpPlanProduct".

 

1. In the Items property, use:

 

If(
    !varShowOpPlanProduct,
    Office365Users.SearchUser({searchTerm: Self.SearchText}),
    With(
        {
            _prefiltered_data: Filter(
                'List B',
                Vendor = cmbVendor.Selected.Value
            )
        },
        ForAll(//filter the Office365 users table to return only users in the List B Manager people field
            ForAll(
                Ungroup(
                    _prefiltered_data,
                    "Manager"//Note we are using the Logical Name
                ),
                Manager
            ),
            First(Office365Users.SearchUser({searchTerm: Email}))
        )
    )
)

 

2. In the Update property of the DataCard, use:

 

If(
    Len(cmbVendor.Selected.Mail) > 0,
    {
        DisplayName: cmbVendor.Selected.DisplayName,
        Claims: "i:0#.f|membership|" & Lower(cmbVendor.Selected.Mail),
        Department: "",
        Email: Lower(cmbVendor.Selected.Mail),
        JobTitle: "",
        Picture: ""
    }
)

 

3.  In the DefaultSelectedItems property of the ComboBox control, use:

 

If(
    !IsBlank(ThisItem.Manager.Email),
    First(Office365Users.SearchUser({searchTerm: ThisItem.Manager.Email}))
)

 

Do not make any other modifications to the other DataCard properties.

 


------------------------------------------------------------------------------------------------------------------------------


If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Imran-Ami Khan

View solution in original post

Again, Amik to the rescue!  Your solution worked like a charm and I'm well on my way now. All data in all scenarios is correctly displayed and updated to the SharePoint list.  I couldn't help but notice you used the original SearchUser (not SearchUserV2).  I tried both -- only the original one worked.  I'm still new to PowerApps but all that I've read and researched so far says to always use the V2.  At this point, I'm not questioning it as I've already wracked my brain enough on just this one field so I'm going with it.

 

I really appreciate your knowledge and taking time to respond!  Thank you, thank you!!!!

View solution in original post

8 REPLIES 8
Amik
Super User
Super User

@StacyO - is there a specific reason you need to use the Patch function on on the OnSuccess property, rather than using SubmitForm?

 


------------------------------------------------------------------------------------------------------------------------------


If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Imran-Ami Khan

with the Submit function all my fields in the form updated on the SharePoint except the people picker so I figured I'd patch it. Is there a better way to do this?

Here are some additional details: Update property is set to ThisItem.Manager and DefaultSelectedItems is Parent.Default.  I'm using a modern form but swapping out with a classic combobox control.  Thanks Amik!

Amik
Super User
Super User

@StacyO - assuming the people field in List A ("Manager") is a single-select people picker, see the blog post I wrote a few months ago on a similar topic using the existing SubmitForm function.

 

https://powerusers.microsoft.com/t5/Power-Apps-Community-Blog/Filter-SharePoint-single-select-People... 

 

You should be able to customise this to suit your needs but if not, feel free to message back. For example, in the Items property of the "Manager" ComboBox control, use:

 

With(
    {
        _prefiltered_data: Filter(
            'List B',
            Vendor = cmbVendor.Selected.Value
        )
    },
    Sort(
        ForAll(
            Ungroup(
                _prefiltered_data,
                "Manager" //Note we are using the Logical Name
            ),
            Manager
        ),
        DisplayName,
        SortOrder.Ascending
    )
)

 


------------------------------------------------------------------------------------------------------------------------------


If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Imran-Ami Khan

You are amazing Amik!  This works when I'm using the filtered results and it writes back to the SharePoint list (no Patching needed). However, when I need to enter a person from AAD, I can enter a user but it won't write back to the SharePoint list.  

Here is my modified formula with your inputs: 

If(
    varShowOpPlanProduct = false,
    Office365Users.SearchUserV2(
        {
            searchTerm: Trim(Self.SearchText),
            isSearchTermRequired: false,
            top: 10
        }
    ).value,
    With(
        {
            _prefiltered_data: Filter(
                'List B',
                Vendor = cmbVendor.Selected.Value
            )
        },
        Sort(
            ForAll(
                Ungroup(
                    _prefiltered_data,
                    "field_8"
                ),
                Manager
            ),
            DisplayName,
            SortOrder.Ascending
        )
    )
)
 
It seems adding the If condition is the culprit?

 

In the field properties, Email isn't an option??? I can force it in the DisplayField property but it still won't show in the layout fields.

StacyO_0-1712101049720.png

 

Am I stuck or is there a way to enter a user manually AND have the filter as well?  Thank you, Thank you!

^^^NOTE:  the Manager field is now ComboBox1

also, curious as to how I can filter out accounts that are disabled in AAD.  I saw something Reza Dorrani published that addressed this so I'll see if I can work it in with what I have.

Amik
Super User
Super User

@StacyO - The Office 365 users table and the SharePoint AD table share totally different schemas. You're going to need to use a separate solution for that scenario by dynamically changing the same table based on the output of "varShowOpPlanProduct".

 

1. In the Items property, use:

 

If(
    !varShowOpPlanProduct,
    Office365Users.SearchUser({searchTerm: Self.SearchText}),
    With(
        {
            _prefiltered_data: Filter(
                'List B',
                Vendor = cmbVendor.Selected.Value
            )
        },
        ForAll(//filter the Office365 users table to return only users in the List B Manager people field
            ForAll(
                Ungroup(
                    _prefiltered_data,
                    "Manager"//Note we are using the Logical Name
                ),
                Manager
            ),
            First(Office365Users.SearchUser({searchTerm: Email}))
        )
    )
)

 

2. In the Update property of the DataCard, use:

 

If(
    Len(cmbVendor.Selected.Mail) > 0,
    {
        DisplayName: cmbVendor.Selected.DisplayName,
        Claims: "i:0#.f|membership|" & Lower(cmbVendor.Selected.Mail),
        Department: "",
        Email: Lower(cmbVendor.Selected.Mail),
        JobTitle: "",
        Picture: ""
    }
)

 

3.  In the DefaultSelectedItems property of the ComboBox control, use:

 

If(
    !IsBlank(ThisItem.Manager.Email),
    First(Office365Users.SearchUser({searchTerm: ThisItem.Manager.Email}))
)

 

Do not make any other modifications to the other DataCard properties.

 


------------------------------------------------------------------------------------------------------------------------------


If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Imran-Ami Khan

Again, Amik to the rescue!  Your solution worked like a charm and I'm well on my way now. All data in all scenarios is correctly displayed and updated to the SharePoint list.  I couldn't help but notice you used the original SearchUser (not SearchUserV2).  I tried both -- only the original one worked.  I'm still new to PowerApps but all that I've read and researched so far says to always use the V2.  At this point, I'm not questioning it as I've already wracked my brain enough on just this one field so I'm going with it.

 

I really appreciate your knowledge and taking time to respond!  Thank you, thank you!!!!

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 (977)