Answered

Filter returns nothing when boolean condition is false

(0) Share

Report

Posted on by PierreCA

364 Moderator

Hello,
I use that code to filter rows in the app.
There's 5 600 rows behind linked to a particular ID.
The behavior is the same when the ID is linked to 1 row.

It works fine until I apply the boolean condition false. Nothing is returned.

Does somebody has any clue?

 Switch(
 filtrerDemandes;
 0;
 Filter(
 Demande;
 f_idEntite.Value = Text( ID_EntiteSelectionee.ID ));


 1;
 Filter(
 Demande; 
 f_idEntite.Value = Text( ID_EntiteSelectionee.ID); demandeActive = true );
 2;
 Filter(
 Demande; 
 f_idEntite.Value = Text( ID_EntiteSelectionee.ID); demandeActive= false)
 
 
 )

Categories:

Building Power Apps

All responses (5)

Answers (1)

Sort by

Ami K 15,689 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@PierreCA -

What control are you using for "ID_EntiteSelectionee" ?
PierreCA 364 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @Amik ,

"ID_EntiteSelectionee" is a local variable containing an ID after making selection in a former screen and is searching an exact numeric value.
Using the Text() formating allowed me to perform the filter without the delegation warning.

When performing the filter as on the picture, I still get a delegation warning.
I don't find a way to circumvent that delegation problem and load the number of rows I want. My understanding of Microsoft documentation (https://learn.microsoft.com/en-us/connectors/sharepointonline/#power-apps-delegable-functions-and-operations-for-sharepoint ) leads me to apply the second option of coding that doesn't work.
Ami K 15,689 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@PierreCA and what is "f_idEntite"? A SharePoint LookUp?
PierreCA 364 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Yes, it is, but with a single choice value.
Verified answer

Ami K 15,689 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@PierreCA - operations on complex data types can be delegated back to the server, but that does not mean all attributes of a complex data type can be delegated back to the server.

For example, the DisplayName or Email attribute of a People data type are delegable, but not the Claims, Department, JobTitle, and Photo attribute.

The same applies to LookUp data types. The "Id" field is not delegable but the Value field is delegable.

Although the SharePoint Lookup field allows users to “relate” a field to another list, complex column types, particularly the Lookup column, are expensive from a performance perspective if you have a high volume of records and are only partially delegable (this functionality was created for the SharePoint user interface in mind).

Given you're expecting users to interact with your data using an app interface, the solution here is to drop the use of LookUp data types and instead use fully delegable data types like Single Line Text or Number to relate your lists together using a common identifier (typically the SharePoint ID).