web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id : QcpIthOMEmIl5w4WwHaP5l
Power Apps - Building Power Apps
Unanswered

How does Filters work with SharePoint Connectors

Like (0) ShareShare
ReportReport
Posted on 10 Nov 2018 20:28:24 by 1,296

Hi

 

I was speaking at SharePoint Saturday Leicester today and we got into a discussion on how does the SharePoint Connector work when you use a statement in PowerApps like ClearCollect(myCollection,Filter(sharepointlist, sitecolumn1 = "MyText").#

 

Does it

1) only bring say 35 rows back from the SharePoint list even though there may be 20,000 rows in the list. (ie the query is done at the SharePoint list.

2) attempts to bring back 20,000 rows into PowerApps, can only bring 2000 rows as that is the max PowerApps can bring back and then tries and filter on the 2,000 rows it actually brought back into PowerApps.

 

Thanks

 

Nigel

Categories:
I have the same question (0)
  • KroonOfficeSol Profile Picture
    587 on 10 Nov 2018 at 21:08:50
    Re: How does Filters work with SharePoint Connectors

    @NigelP

     

    The = parameter is delegatable to SharePoint (See docs for delegation info), so 1 is probably a yes. As soon you try to do this with a parameter which is not delegatable 2 is a Yes.

     

    In general what I do when I add a gallery and want to filter the items I split it up in delegatable and non-delegatable filters. Then I do like this:

    • On the delegatable filters search box I only tricker a toggle on the OnChange attribute.
      On this Toggle.Change I do a ClearCollect from my datasource with only the delagatable filters.
    • The Collection I have in the items off my gallery
    • The non-delegatable filters I add there.

    To make this work I add a flat number field to my SharePoint list for each related complex Field. I write the ID from the related list to this number field, as well as the record to the related complex field. This means I always can filter on this ID number field if I want and don't have to worry about the delegation limitations.

     

    Oke you are still limited to 2000 records, but I figure no way that more then 2000 records are relevant on any given time. Off course when you want to sum() numbers it can be a problem, but with that amount off records needed you should not be in SharePoint, but move to SQL Server in my opinion. 

     

    By the way it's correct that you can bring max 2000 records in directly from PowerApps. But you could increase this to 5.000 records if you need when you use Flow as an interface between PowerApps and your Sharepoint List. 

     

    Hope this helps.

     

    Paul

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Tom Macfarlan – Community Spotlight

We are honored to recognize Tom Macfarlan as our Community Spotlight for October…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 885 Most Valuable Professional

#2
developerAJ Profile Picture

developerAJ 571

#3
Michael E. Gernaey Profile Picture

Michael E. Gernaey 352 Super User 2025 Season 2

Last 30 days Overall leaderboard