cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Continued Contributor
Continued Contributor

Re: Filtering Peoples Column in a SharePoint List

So yes, it does this w/ a People column as well.  I did the following example:

image.png

I created a SharePoint table w/ a Person field.  Added a record w/ my user selected.  Then tried this query for a label.

So in "People" fields also throw delegation warnings.

Highlighted
Helper III
Helper III

Re: Filtering Peoples Column in a SharePoint List

@jhall it is a "Person or Group" Data field. 

so basically i need to filter the list that contains this Person or Group field and in that context  i also need to filter on a specific value in that field without getting the delegation error

Highlighted
Frequent Visitor

Re: Filtering Peoples Column in a SharePoint List

Any ideas how to overcome the delegation warning in such case. Would be nice to filter on Poples column with all the benefits of delegation. Any solutions or workarounds?


@jhall wrote:

So yes, it does this w/ a People column as well.  I did the following example:

image.png

I created a SharePoint table w/ a Person field.  Added a record w/ my user selected.  Then tried this query for a label.

So in "People" fields also throw delegation warnings.


 

Highlighted
Continued Contributor
Continued Contributor

Re: Filtering Peoples Column in a SharePoint List

Again, haven't watched or tested this, but this looks like it is a method to pull data directly from AD and ?maybe? won't get a delegation warning.

https://www.youtube.com/watch?v=xs_hWRNCwuA

Or potentially try the Office365Users connector?  I'm just guessing now.  😄

Highlighted
Continued Contributor
Continued Contributor

Re: Filtering Peoples Column in a SharePoint List

I will say, I just tested using the Office365User connector.  I tested the following below and assigned it as the DataSource for a ListBox and do not get a delegation warning (and note that we're the largest non-governmental employer in our US State - and "Hall" is a pretty popular name).

Office365Users.SearchUser({searchTerm:"Hall"})

So it appears that this can be a way to get around some delegation warnings for populating DropDowns and ListBoxes, but of course, if you're doing some kind of match/lookup on values in SharePoint for a particular user name, then that's still not going to save you from encountering this.

Helpful resources

Announcements
secondImage

New Return to Workplace

Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Check this Out

Helpful information

Featuring samples like Return to the Workplace and Emergency Response Applications

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (6,453)