Answered

Filter Person Field that is Blank while avoiding Delegation

(0) Share

Report

Posted on by landonjochim

256

I have a Gallery in my PowerApp that is pulling back a filtered SharePoint List. Currently I am getting a delegation warning when I use a IsBlank(PersonField). So I am trying to work through this and the warning goes away if I do PersonField.DisplayName="", however this does not filter the list and remove the items that the PersonField is Blank/Empty.

SharePoint List name: PurchaseRequest_PurchaseRequestList

Results needed:

'Submitted by' = Me

And either

Status = "Pending"

'Assigned to' = [empty] AND Status = "Approved"

The 'Submitted by' field and 'Assigned to' fields are both Person/Group fields within the SharePoint List. 'Status' is a choice field.

Here is my formula that is returning the filtered data correctly, but is giving me delegation warnings:

Sort(Filter(PurchaseRequest_PurchaseRequestList, 'Submitted By'.Email=currentUserProfile.mail && (Status.Value="Pending" || ((IsBlank('Assigned To') && Status.Value="Approved")))), Submitted, Descending)

Here is my formula that is returning items that are 'Submitted by' = Me and 'Status' = Pending. However, it is not returning the ones where 'Assigned to' = [empty] && 'Status' = Approved. But I am not getting any delegation warnings with this formula.
Sort(Filter(PurchaseRequest_PurchaseRequestList, 'Submitted By'.Email=currentUserProfile.mail && (Status.Value="Pending" || (('Assigned To'.DisplayName="" && Status.Value="Approved")))), Submitted, Descending)

I am ultimately looking for a way to check if the 'Assigned to' field is empty/blank without causing delegation issues. and yes, my list is > 2000 and I need to be able to return those items so increasing the data row value is not an option.

Thanks!

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

Sort by

WarrenBelz 155,983 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @landonjochim ,

Complex field types such as Person Fields are not Delegable - there is a way of getting rid of the warning, but this will simply work only on list sizes up to your Delegation limit.

I have a blog on Delegation that may assist with some workarounds.

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.

Was this reply helpful? Yes No
Verified answer

landonjochim 256 on at

Like
a
(0)

Report
Copy link

Link copied!

@WarrenBelz - Thanks for the response. I ended up opting for using a collection on load of the screen. I performed all my delegable filtering in the clearcollect and then only did my non-delegable filtering on the collection. Works great.

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

Like
a
(0)

Report
Copy link

Link copied!

Thanks @landonjochim ,

That is the way I was referring to . . .

Was this reply helpful? Yes No
twolf2286 12 on at

Like
a
(4)

Report
Copy link

Link copied!

I know this is a bit old but for anyone else who finds this thread another option would be:
PersonField.DisplayName = Blank()

Was this reply helpful? Yes No
Curioler on at

Like
a
(0)

Report
Copy link

Link copied!

Works like butter! Thanks a ton. 🙂

Was this reply helpful? Yes No