Hi! You can use two collections and then join them together. Given you have some sort if ID to sort on. I created one to combat this issue.
Concurrent( ClearCollect( Collection1, Filter( Table1, ID < 2000 )),
ClearCollect( Collection2, Filter( Table1, ID >= 2000 && ID < 4000 )),
ClearCollect( TableX, Collection1, Collection2 )
The question is always why do we need this many data points? So I sorted by ID based on records which had been touched at all, so any records beyong 4000 which hadn't been touched do not appear in my power app.
& then use TableX ,Hope this helps! Jese
Hi @abd3127 ,
Thanks for asking--my solution is very dated. I created it at a time when I needed to aggregate my data. I needed to perform a sum against the entire data source. At the time, there were not ways of doing this as I would hit delegation issues. So I pulled in all the data I had at the time, which was thousands of records and not very performant. Now, I've overcome those issues with SQL Views and aggregates in the Common Data Service.
I would not suggest pulling in all of that data today even if you could. When designing an app, you should only bring in the relevant data to keep the app as lightweight as possible. You can search for some patterns on this forum for filtering your data further to minimize the load.
@abd3127 I built a solution for this for SharePoint Lists last week but would agree with @Mr-Dang-MSFT and question why you need all the data getting collected into your App. The solution for SP users is to get PAs to capture SP Views thereby saving the Filter() / Sort() / etc delegation issues.
My solution isn't overly elegant but it works and here it is (apologies for the long post):
The solution is to use SharePoint ID numbers.
1. First, sort by ID Descending, collect that into collection1 (col1)
2. Then, sort by ID Ascending, collect that into collection2 (col2)
3. Build an array of 'Missing ID numbers' as a collection - call it colTarget. Calculated by (MinID col1) - (MaxID col2)
4. Use ForAll() with Collect() to get the missing ID rows one by one into collection3 (col3)
5. [optional] Collect col1, col2 & col3 into finalCol
Step 4 can take awhile if 'the gap' between Min/Max is large so just be mindful of that. I put a label in my Dev App (see below pic) and set it to CountRows(col3) and you can see it tallying up as data gets collected - gives you an idea of data collection speed.
You could always build a smaller array (Step 3) of missing IDs that gets tacked onto col1 if you don't need all of the data Eg. (MinID col1) - 500 instead of (MinID col1) - (MaxID col2)?
//specify target rowcount
//define a base collection from which you will generate your target collection. A colBase of 60 will be able to collect up to 60x60 = 3600 items. Set colBase's size to meet your needs.
//setup collections to be used as inner and outer counters
//generate array of missing ID numbers
RemoveIf(colTarget,RowId>=Min(col1,ID)); // remove unwanted ID numbers from ID array
ClearCollect(finalCol, col1, col2, col3)
As I say, not elegant but effective.
And the pic of my Dev App counting fields
Hope this helps.
You have to build more than 1 collction.
And then join the collections together to build a dataset of the combined data.
Collections store the data on Entry,in the cache.
Your Filter() code on ID still won't get more than 2000 records from Sharepoint. This is a limitation within PowerApps.
As a test, I ran your code on a SP list that I have access to with over 4500 records and the stats speak for themselves - only 2000 records total returned by PowerApps. I have set the data row limit to 2000 in Adv settings.
I had similar requirement and took a slightly different approach.
Instead of a combo box, I use a Gallery with a text 'searchbox' above.
The gallery populates with the first 50 items from D365 that contain the text in the searchbox.
SortByColumns( ShowColumns( FirstN( Search( Filter( Accounts, 'Account type' = 866100002 ), txtSearchGalAccounts.Text, "name" ), 50 ), "name", "accountid", "accountnumber", "_fbh_accounttypece_label", "_fbh_primaryaddress_value" ), "name", Ascending )
When the user clicks on an entry in the Gallery, the entry is selected and passed to the relevant screen/control.
Advantages: Deals with any number of records - if >50 items returned, user should just keep typing to make the search more specific, users find a Gallery much easier to use on mobile devices (where the combo box is a UI nightmare).
Disadvantages: Must be online, every search is querying D365 directly, results can take a few seconds to appear.
I have been getting delegation warning in my dropdown,comboboxes and gallery and reason is showing up beacuse of "in" operator. Also there is more than 2000 records in my sharepoint list. So where should i put above code? In dropdown.items or in Screen.Onvisible? I am a bit confused on that part. Help me out here.
You need to collect all your sharepoint data into collections in the App first then run your dropdowns, combos, galleries off of the collections not your SP list. That way 'in' should work for you.
Run my code in the App start or Screen.OnVisible properties
Find your favorite faces from the community presenting at the Power Platform Community Conference!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021