Answered

Power Apps Formulas - Filter Error?

(0) Share

Report

Posted on by Florida712

Hello,
I think I encountered an issue with the "new" Formulas.
I have this Formula:
_fxInspectionRecords = Filter('FPO ENV Refrigerant Usage Trackings', !IsBlank('Location/Block'));
It filters ok but the resulting table ONLY contains the value for the Location/Block column not the other columns for the filtered records. When looking at the content of the formula it does show all columns of the dataset but only the values for the Location/Block-column (the other columns do have values in Dataverse).

I came across this trying to remove a delegation warning
Previously I assigned all the records to the Formula:
_fxInspectionRecords = Filter('FPO ENV Refrigerant Usage Trackings') (instead of using a collection)

This formula for Gallery Items then leads to a delegation warning for the If-sections. I use the same formula for a different Formula that is based on ShowColumns (so i thought that maybe I cannot just assign a complete datasource to a Formula and that is why I tried the filter command that leads to be error above.

Filter(
colInspectionRecords,
IsBlank('cmbFilterLocation-ER'.SelectedItems) || cgfpo_location in 'cmbFilterLocation-ER'.SelectedItems,
If(
'chkFilter<50-ER',
cgfpo_capacity_50_plus = false,
cgfpo_capacity_50_plus = true
) || If(
'chkFilter≥50-ER',
cgfpo_capacity_50_plus = true,
cgfpo_capacity_50_plus = false
))

My dataset is well outside the delegation concern, but I would to understand the strange behavior, especially for the
_fx = Filter() part.

Any help or idea is appreciated.
Thank you

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

BCLS776 8,994 Moderator on at

Like (1)

Report

You are likely seeing the effects of explicit column selection bringing in only the minimum necessary columns to complete the operation. If you wrap the Filter() in a ShowColumns() statement you will force it to bring in additional columns that you specify.

Hope that helps,

Bryan

Was this reply helpful? Yes No
Florida712 78 on at

Like (0)

Report

Thank you Bryan. I had hoped to avoid specifying the columns as it is a large number of columns. I do find it strange that not specifying leads to automatic exclusion not of the columns but the values being blank.
Do you have any idea on whether utilizing ShowColumns will avoid delegation issues? The behavior from my original formula leads me to believe that being the case.

Was this reply helpful? Yes No
Verified answer

BCLS776 8,994 Moderator on at

Like (1)

Report

@Florida712 wrote:

Thank you Bryan. I had hoped to avoid specifying the columns as it is a large number of columns. I do find it strange that not specifying leads to automatic exclusion not of the columns but the values being blank.
Do you have any idea on whether utilizing ShowColumns will avoid delegation issues? The behavior from my original formula leads me to believe that being the case.

Yes, a Filter() on a Dataverse record will read the column schema and show blank values.

You can turn explicit column selection off for the entire app, but you would give up the performance benefits that come from using it. It is located in the app settings. Try to avoid turning this setting off if possible.

Another option when using Dataverse, and I do this whenever I have a complicated or troublesome Filter(), is to use a Dataverse View to set up the filtering in the backend. It helps app performance in real-time too because it reduces the amount of records a non-delegable Filter() may have to load and sort through.

Bryan

Was this reply helpful? Yes No