Use multi-people-picker column to create power apps collection

[Schwartz_Cory]

Hi,

Use case:

Users need to select from a list of specific VPs of my company for an approval of a form they submit via PowerApps

Solution:

• Created a SP-List to manage the VPs in a multi-people-picker column for Form ID=9 (multiple forms have this same use case)
• Collect all VPs from ID=9 AND in the VP people picker column, and add them to a collection in Power Apps.

Issue:

I am able to collect the information I need, but it throws it into a nested table. How do I unnest this table so I can use it in a Gallery so users can select a VP?

Code in the App.OnStart Field:

Collection:

(why is there a VicePresidents table inside this collection? why isnt the "ApprovingVPs" collection THAT table?)

[SebS]

@Schwartz_Cory 

You can't un nest it Person and Group column is a complex type and the Person picked is a table containing information like Name, Department, Role, Email and more. 

To get only names You should run ForAll and point to DisplayName what will then collect only names from all Picked People in the Picker

[Schwartz_Cory]

Hi @SebS ,

I would like all columns in the multi-people picker table, but I definitely need the Name, Email, Picture.

How can I use the ForAll function to get those 3 into a Single-level collection (no nested collections)?

[Schwartz_Cory · Accepted solution]

Found a solution!

You need to create another collection based off the initial collection

See code screenshot below: (using "Managers" Instead of "VPs" now).

The 1st clearcollect function is getting the SP-List People Picker Column from ID#9.

The 2nd Collect function is just creating a seperate collection based off the nested collection. (This allows me to use it in a Gallery as the nested collection does not work)

(more screenshots below)

1st Collection

2nd collection (what i needed this whole time for my Gallery) (drew over it to protect identity)

[SebS]

@Schwartz_Cory 

Nice Well done 🙂

[Schwartz_Cory]

Also, I am able to make this more efficient and remove Collection1 by replacing it with my Filter(SP-List) function:

So now I dont have 2 collections and only the 1 I need!