Search function in power apps

[yougan]

I have a list called "LL" and I am trying search Field  5  in the Title column using below search query, but not working

Please help where I am doing wrong 

and other requirement is  I want to see all the items includes with number 5, example:  5 ,15, 25, 35  in Power apps. Please help 

[eka24]

Insert a TextInput name example: TextInput5

On the Items property change the code to:

Filter(LL,Title=Value(TextInput5.Text))

Or using your current formula in the screenshot:

Filter(LL,Title=10)

On your second request, try this on the Items of the gallery:

Filter(LL,Title in [5,35,15,25])

------------

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

[yougan]

 Hi Eka,

Thank you for the response. I got the output. But why warning is coming up. Please help to sort out this warning. 

I have attached warning message. 

[WarrenBelz]

Hi @yougan ,

Firstly, the Title column is by Default a Text field and the "numbers" are actually stored as Text, so your filter should be

Filter(
   LL,
   Title="10"
)

On the second one, using the same logic

Filter(
   LL,
   "5" in Title
)

You will get a Delegation warning on this due to the in Filter not being Delegable, so if you have less than 500 items in the list, yo can do this

With(
   {wLL:LL},
   Filter(
     wLL,
     "5" in Title
   )
)

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[yougan]

Hi Eka,

But in my power apps settings it is set to 500 , then why it is showing warning?

As you know I have list, which has around 24000 items with only title column with 1 to 24000 values 

I see setting is set to 500.

can you give me few examples of delegable functions where it does not show warning

and can you give me some examples of delegable functions where it does show warning 

is warning symbol showing because filter has to process more than 500 items in the SharePoint? 

because filter only for 10 correct? it has only one item 1 value with 10 from entire 24500 items? but still it is showing warning symbol why? 

suppose it has 10 value items more than 500 then it would show right? 

what you have given in the out put 

[poweractivate]

@yougan 

---

@yougan wrote:

is warning symbol showing because filter has to process more than 500 items in the SharePoint? 

because filter only for 10 correct? it has only one item 1 value with 10 from entire 24500 items? but still it is showing warning symbol why? 

suppose it has 10 value items more than 500 then it would show right? 

---

No, this is not the correct way to understand this aspect of delegation. The delegation does not operate on the number of results returned. It operates on the total number of entries to begin with.

The non-delegable query will only see items 1 to 500 (or, if you change it to 2000, only 1 to 2000) of the total data set BEFORE even running the query.

Suppose you have 24500 items. Suppose your match is item# 24499. It doesn't matter that your filter will only return one match. Yes, one match is far less than five hundred matches. Doesn't matter anyway.  Match for Item #24499 will not return because only items # 1-500 are checked to begin with. So no match will return.

Therefore the answer is you must not use  non-delegable queries at all if you have a data set larger than 500 entries. The non-delegable limit can be increased, but the max it can be increased to is 2000. If your dataset is more than 2000 entries, you MUST use delegable queries that do not give the yellow triangle warning or it will not behave as expected at all.

For any further elaboration, you can reply here. There is more you should also understand as well regarding this one. We are unsure if we could be available right now to provide any further detail about this thread, so we might want to prefer to see if @WarrenBelz or @eka24  to clarify anything further.

We would also suggest you take a look more carefully again at the responses that both of them gave you so far as well since even just those responses so far could probably help you.

[yougan]

Hi Dynamics Edge,

Thank you for the response.

who will decide it is delegable query and it is not delegable query?

Based on what it is decidable that it is delgable function or non delgable function? 

in my case I have only one entry with 10 in the entire list having 24500 items, why it is showing warning? 

[poweractivate]

---

@yougan wrote:

in my case I have only one entry with 10 in the entire list having 24500 items, why it is showing warning? 

---

Once again as we stated it doesn't matter how many you will have. If it is not delegable it will only see 500 records. Again, it is irrelevant how many the filter will return. It matters how many total you have altogether.

Also, some more detail: not delegable means the data source does not support to perform the direct corresponding operation being requested from PowerApps in the formula, with any currently compatible backend API for that specific connector. So Power Apps have to resort to manually bring the whole data in. For stability reasons, Power Apps do not allow to bring the whole entire records in that case as it would not perform correctly and overflow the local memory of the device.

---

@yougan wrote:

who will decide it is delegable query and it is not delegable query?

---

It depends on the specific data source and the backend API support and the complexity and commands issued from the formula in question, and many other factors.

Sometimes just rewriting the formula in very specific ways will make the warning go away and it becomes delegable even in cases where it appears not to be possible to make it delegable. Specific subtlety in writing of the query can help. This sometimes would require anywhere from simple to advanced advice and depends on the scenario.

If even doing a rewrite of the formula does not work, in general you should just change the whole data source then. Dataverse (previously known as Common Data Service) is likely the best one out of all of them for support of delegation. Some other ones like SharePoint could be acceptable well. If testing the formula with data in the Dataverse (Common Data Service) data source still gives the warning, the formula should probably be re written in that case.

Hope this helps. In case you are still not clear in this matter, you could let us know in case.

[yougan]

Hi Dynamics Edge,

Thank you for the explanation. some how I managed to understand. But I have few more quries can you please clarify those also

So do we have any way to get a query which will not give warning symbol for the data set having 25000 items(sharepoint)?

how do we make sure to supply a meaningful query for large data sets? ( having more than 2000 items in sharepoint )

if it shows warning symbol does it mean we need to amend the forumlae? or is it okay to accept the result and not much bother about it?
(beacuse I see result showing correctly )

so what if sharepoint source is having 1 lakh records, if we want to get a result with out warning?

[WarrenBelz]

Hi @yougan ,

I have done a  blog on Delegation that may explain some of your questions.

The one thing I can tell you now is that you cannot use the in Filter on 24,500 records.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.