Power Platform Community Forum Thread Details

I have found cases in the past where using a With() statement can mask the non-delegable warning. I have a case where everything looks good, but when I bring up the monitor, I see this:

In this case, it appears 2000 rows (My row limit setting) are being queried. Does this mean if my table is 5000 rows, that I'm not getting a full filter result?

See? It all looks happy here. VIEW_ODERBOARD_DATA is a SQL view. I know that the 'in' condition is supported with delegation. I have used it successfully in the past with text datatypes.

Or, do I not need to worry about this?

Categories:

Building Power Apps

@martinav
I think it's because the CountRows function is not delegable to any data source (except Dataverse).

I believe CountRows is only delegable in Dataverse specifically only, and only when the Enhanced Delegation for Dataverse setting is turned on.

However even in Dataverse with the Enhanced Delegation for Dataverse setting turned on, there are certain caveats to using CountRows in particular, as described in the official documentation linked above.

You say that when you use With, it masks the delegation warning for you.

When you don't use nested With scopes )or any With scopes at all) and intentionally repeat everything overtly, does the delegation warning for CountRows appear then?

If so, I may recommend as a workaround to write it without the With scopes, then when done testing and writing the formula, use your With scopes after that.

I am not sure if perhaps it is expected behavior or not but I guess you can ask Microsoft here if not sure.