Filter functions that use in operator and Filter return value in conditional expressions do not finish processing.

[Fuku-Shima]

When I click the button with the following code set to OnSelect, the content of the retrieved CollectionC is fine, and the Notify message is displayed correctly.

ClearCollect(
    CollectionA,
    Filter(SharePointListA,ClassCode = 1)
);
ClearCollect(
    CollectionC,
    Filter(
      AlreadyAcquiredCollection,
      ItemCode in CollectionA.ItemCode)
);
Notify(Text(CountRows(CollectionC)));

However, if the following code is set to Button.OnSelect and clicked, the process does not complete and no message is displayed.

The state of the button will remain selected (grayed out).

ClearCollect(
    CollectionC,
    Filter(
      AlreadyAcquiredCollection,
      ItemCode in Filter(SharePointListA,ClassCode = 1).ItemCode
    )
);
Notify(Text(CountRows(CollectionC)));

I am guessing that this phenomenon is due to a bug.
The version I am using is 3.22013.7.

Please reply with reports of similar phenomena, advice on how to deal with this, and any related information.

[WarrenBelz]

Hi @Fuku-Shima ,

Try the below - same result with only one collectiuon

With(
   {
      w1:
      Filter(
         SharePointListA,
         ClassCode = 1
      )
   },
   ClearCollect(
      CollectionC,
      Filter(
         AlreadyAcquiredCollection,
         ItemCode in w1.ItemCode
      )
   )
);
Notify(
   Text(CountRows(CollectionC))
);

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.

Visit my blog Practical Power Apps

[Fuku-Shima]

Hi @WarrenBelz 

Thanks for the reply.

With the method you presented, I was able to get the correct results without the process stopping.
I think I will use this for a while for now.

Do you have any idea why the code I posted did not work properly (or why it works fine with With)?

[Fuku-Shima]

I observed the behavior in detail.

When running the above code, the behavior was different depending on the number of AlreadyAcquiredCollections.
In the case of about 1000 items
　It works fine.
In the case of about 3000~5000 items
　Most of the time it works fine, but sometimes the process stops as described above. In any case, there is no error message.
In the case of 10000 items
　As far as I have tried, the process stops as described above.

Also, I observed the behavior with the Monitor tool.
Even when I set the AlreadyAcquiredCollection to 10000 and the process stops,
Filter(SharePointListA,ClassCode = 1)", which retrieves data from the network, seems to complete the process without any problem. There were no network errors.
As far as I can tell from the Monitor tool, there is no difference in the logs between successful and unsuccessful cases.

[WarrenBelz]

Hi @Fuku-Shima,

Now you mention the number of items, the issue with your original code is that it is not Delegable (the entire filter) as SharePoint will not Delegate relational queries. The code I supplied also has some (but fewer) limitations in that the With() statement (which is essentially a table / collection) will only hold up to your Delegation limit after the delegable filter is applied, so you have a maximum of 2,000 items to work with. You can then however do whatever filter you want on this data set without any Delegation restrictions. I have a blog on this process if that is useful to you.

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.

Visit my blog Practical Power Apps

[Fuku-Shima]

Hi @WarrenBelz 

Thanks for the reply.

I don't think the delegation issue has anything to do with this phenomenon.
The reason is as follows

• The "AlreadyAcquiredCollection" is a collection that has already been acquired locally. (I used ForAll, etc. to generate a collection of 10,000 items.)
  If I check the contents of this collection, I can see that I have obtained ID1~10000.
• Filter(SharePointListA,ClassCode = 1) is successful as far as the Monitor tool is concerned. getRows request contains a filter query for "ClassCode = 1", and getRowsCount shows the actual number of data.
  However, the subsequent ClearCollect does not show up in the log.

I assume this is a bug in the Power Apps version, since the process continues without stopping the browser or getting an error.

[WarrenBelz]

Hi @Fuku-Shima ,

It has everything to do with Delegation (your original code) as your relational query was to SharePointListA, which is completely not Delegable and therefore rendered the entire query not Delegable.

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.

Visit my blog Practical Power Apps

[Fuku-Shima]

I'm sorry about that. It seems that the conversation has gotten complicated.
I'll write down my thoughts as a supplement.
I hope the development team will be able to address this.
I'm sorry  @WarrenBelz , but this post is an issue report, so I will not make it resolved. (I deeply appreciate your suggestion of a workaround to use the With function.)

Supplemental:

• I am not planning to register more than 2000 items in SharePointListA. So I'm not worried about the problem of not being able to delegate (i.e., not being able to retrieve data that exceeds 2000 items).
  (In fact, it would be preferable to be able to delegate, but that is a different topic from this bug report.)
• I've been able to work around this bug so far by using the Message 2 approach. However, I don't technically know why the process stops in my code.
• The problem is that the process stops after getRows and getRowsCount are completed. Even if this is not a bug, it is at least a problem regarding the fact that the browser does not stop or display an error.

[WarrenBelz]

Hi @Fuku-Shima ,

It is still better to not have Delegation warnings, but I have no further ideas on this.