Unanswered

SQL Delegation with IsBlank and multi layer filtering?

(1) Share

Report

Posted on by BrianHFASPS

732

I am trying to workaround the inability to delegate filtering to SQL with IsBlank. One idea was to do my primary filtering (table size reduction) on another filter and then do a surrounding filter with the IsBlank. I still see a delegation warning. Is PowerApps merging the filters into one SQL call?

Filter(
 Filter(
 '[dbo].[Today Activity Attendance]',
 'Grade Sort' < 0
 ),
 Not(IsBlank(MorningSigninTime))
),

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

BrianHFASPS 732 on at

Like
a
(2)

Report
Copy link

Link copied!

Are you saying that my code will work to reduce initial size on query response and not to worry about outer filter delegation warning?

Was this reply helpful? Yes No
cwebb365 3,294 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

If you want it clean without errors, you can just utilize WITH function. Something like this.

With( {TodaysAttendance: Filter('[dbo].[Today Activity Attendance]','Grade Sort' < 0)},

Filter(TodaysAttendance, Not(IsBlank(MorningSigninTime)))

This will basically get a temporary variable of the delegable data into TodaysAttendance, then run the 2nd filter inside powerapps which doesn't need delegation. However, thing to note, is you can still only return 500 default up to 2000 records with the setting of records for the first query.

Either way works, I prefer WITH as I can do more with that data being stored locally.

Was this reply helpful? Yes No