the non-delegable row limit set in the experimental feature. impact on filter in sharepoint list ?

[nicointhebox]

Hello

I try to understand the limit of delegation between powerapps - sharepoint list and use of collection.

I set the experimental future on powerapps to 3

I have a sharepoint list (FR_FAMILLE) of 20 occurrences that I linked to a dropdown (not in a form) 

Issue that I do not understand is why do I see only 3 occurences in my dropdown using a delegable qery

on dropdown ITEMS : Filter(FR_FAMILLE;Business="Granulat") - no delegation warning..

same result if I just do "FR_FAMILLE" on items

aka "FR_FAMILLE" is my sharepoint list

aka "Business" is a text field what I use to filter in/out occurences.

powerapps retrieves only 3 instead  of 20...

If I use a datatable with the same code and same setup I got my 20 results... same using gallery !

Note : I tried to use collect but as it is non delegable function I got the same result 3 (For this case I underdstood the reason)

Can you explain me why I got this behavior on a dropdown / combobox....

[v-siky-msft · Accepted solution]

Hi @nicointhebox ,

To better understand your issue:

1. you have set the value of data row limit for non-delegable queries to 3, right?

2. when you use a filter function which should be delegable, the dropdown only show 3 items ,right?

This issue is caused by the search part of combo box, not the formulas you are using. As we can known that from the image below, the Search function is not delegable in sharepoint.

We can also find the delegation warning in powerapps, although the formula we use is delegable, but there is still a delgetaion warning to combo box searchitems when data source of combo box is sharepoint.

So this is why you have only three items in your combo box, i think. I haven't found an appropriate explanation for dropdown, but I think it should be the same as combo box, which is caused by dropdown itself.

Hope this can help.

Best regards,

Sik

[nicointhebox]

Thank you for your explanation
Hope a new release will fix the issue