Answered

Show items in combobox based on multiselect person or group field

(3) Share

Report

Posted on by Iantaylor2050

603

I have a combobox where i need to show the items based on certain columns. Below is the code. This works fine with person or group column which are single select. like SO, BO, Name of requestor.

I need to open up the combobox also for multiselect person or group field named 'Team Members'.

I tried User().Email in 'Team Members'.Email but it doesnt work. May i know how to modify the below code?

Combobox Items

Filter(
    Detailed_List,
    ('Name of Requestor'.Email = User().Email || SO.Email = User().Email || BO.Email = User().Email )&& 'Status of request' = "Request Processed" && Request_Type = "Finance"
)

Categories:

AI Builder

Building Power Apps

Connector development

GCC, GCCH, DoD - Federal App Makers (FAM)

Error handling

Microsoft Dataverse with Power Apps

Experimental features

Governance & administering

Power Apps Pro Dev & ISV

General topics

Power Query

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Suggested answer

Fredrik_A 3,644 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!
Hey,

give this a try:

Filter( Detailed_List, ( 'Name of Requestor'.Email = User().Email || SO.Email = User().Email || BO.Email = User().Email || !IsBlank(LookUp('Team Members',Email=User().Email)) ) && 'Status of request' = "Request Processed" && Request_Type = "Finance" )

If my response solved your issue, please mark it as ✅ Accepted Answer and give it a like.

Was this reply helpful? Yes No
11manish 3,333 on at

Like
a
(1)

Report
Copy link

Link copied!
Since 'Team Members' is a multi-select Person field, it must be treated as a table.

The correct and optimized way is to check whether the current user exists within that table using !IsEmpty(Filter(...)).

For better performance and readability, use a With() block and normalize email casing.

Keep in mind that this approach is not fully delegable, so for large datasets, consider moving the logic to backend processing or redesigning the data model.

try below:

With( { _userEmail: Lower(User().Email) }, Filter( Detailed_List, ( Lower('Name of Requestor'.Email) = _userEmail || Lower(SO.Email) = _userEmail || Lower(BO.Email) = _userEmail || !IsEmpty( Filter('Team Members', Lower(Email) = _userEmail) ) ) && 'Status of request' = "Request Processed" && Request_Type = "Finance" ) )

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @Iantaylor2050,

For multi-select person columns you need the `in` operator, which checks if a value exists anywhere in the column of a table. Try this:

```
Filter(
Detailed_List,
(
'Name of Requestor'.Email = User().Email ||
SO.Email = User().Email ||
BO.Email = User().Email ||
User().Email in 'Team Members'.Email
)
&& 'Status of request' = "Request Processed"
&& Request_Type = "Finance"
)
```

The key difference: single-select person columns return a single record so you use `.Email = User().Email`. Multi-select returns a table of records, so you use `User().Email in 'Team Members'.Email` which checks if the user's email exists in that table.

One thing to be aware of: this part won't delegate to SharePoint. You'll get a delegation warning and it will only check against the first 500 (or 2000 if you raised the limit) rows. If your list is small that's fine. If it's large you'll need a different approach like storing Team Members as a separate related list or using a calculated text column.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @Iantaylor2050,

Firstly, @Valantis is correct in the structure, however you will have a Delegation issue (you will get a warning as well) as the in operator is not Delegable. There is no workaround directly for this, however you can "pre-filter" with your Delegable other criteria: -
With( { _Data: Filter( Detailed_List, 'Status of request' = "Request Processed" && Request_Type = "Finance" ) }, Filter( _Data, User().Email = 'Name of Requestor'.Email || User().Email = SO.Email || User().Email = BO.Email || User().Email in 'Team Members'.Email ) )

So providing the top filter returns (the list can be of any size) less records than your (500 - 2,000) Data Row Limit, this should return all expected records.

Please ✅ Does this answer your question 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 answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
Verified answer

WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Iantaylor2050,

A quick follow-up to see if you received the answer you were looking for. Happy to assist further if not.

Please ✅ Does this answer your question 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 answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No