Delegation warning with simple LookUp

(2) Share

Report

Posted on by Chris-D

1,246

Why is this a delegation warning?

 With({
 // Look up one record
 DeviceRecord: Last( Filter('App Config Devices', Title = Serial))
 },
 ... do things ...

 // Check QA record exists
 If( IsBlank( LookUp('App Config QAs', Device_List_ID = DeviceRecord.ID)),
 UpdateContext({ Message: "NO QA RECORD"});
 );
 
 ... more things ...

Device_List_ID is definitely a number, and so is DeviceRecord.ID. If I use 'Device_List_ID = 4' (or any other number) in the LookUp there's no problem.

I've tried using Value( DeviceRecord.ID) but that doesn't fix it.

Stumped.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Chris-D 1,246 on at

Like
a
(1)

Report
Copy link

Link copied!
This is not the answer. Please read the question.

The problem is not with the LookUp function. If I replace DeviceRecord.ID with a number, it works:
// Delegation warning LookUp('App Config QAs', Device_List_ID = DeviceRecord.ID) // No delegation warning LookUp('App Config QAs', Device_List_ID = 73)

A simple LookUp with this=that should not cause a delegation warning no matter how big the data set.

Was this reply helpful? Yes No
Verified answer

timl 37,287 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @Chris-D

Power Apps isn't able to delegate a condition that references a property of record (eg, ID).

If you extract the Id value inside your With block, the resultant Lookup should be delegable.

With({ // Look up one record DeviceRecordId: Last( Filter('App Config Devices', Title = Serial)).ID }, ... do things ... // Check QA record exists If( IsBlank( LookUp('App Config QAs', Device_List_ID = DeviceRecordId)), UpdateContext({ Message: "NO QA RECORD"}); ); ... more things ...

Was this reply helpful? Yes No
Chris-D 1,246 on at

Like
a
(0)

Report
Copy link

Link copied!

Perfect, thanks for the explanation @timl.

I'm not sure why using Value(DeviceRecord.ID) didn't fix it though, wouldn't PowerApps execute the Value function first and pass that to the LookUp expression as a number? Do you know the reason for this?

Was this reply helpful? Yes No