Hi,
There are a few old posts on collection row limits but as these appear to have gone stale I thought I'd start a fresh version.
I've always worked on the basis that collection size (and any data returned from tables etc.) is limited by the Data Row Limit setting set in the app - the default is 500.
Some context.
I'm currently working on building a PowerApp that connects up to multiple data sources, a legacy on-premise Oracle data base being one (with over 10 years of data). As is typical this is a normalised database and requires several table joins to provide person friendly information.
Bumping the row limit to 2,000 still see many of the tables hitting this limit and unable to display all of the data.
Filtering the data has been a challenge as to get the data needed requires joining six or more tables BEFORE you can filter it (normalised data on steroids). Consequently, you get a lot of data missed/lost.
Switching to Flow to do the heavy lifting I've created a SQL/Query to make the table joins and take a variable from the app to filter it.
This flow is called directly from the app with the Response added to a collection, for display and further refinement.
This all works great and is very fast.
What I'm confused with is that although I have the app row limit set at 500, the count rows for the collection returns significantly over 500, in one case 2,750.
I don't want to manually count 2000+ rows to manually check.
My question is... is this a true count?
If the answer is yes...
Why does the response from a Flow bypass the app row limit?
Is there a maximum number of rows that can be returned this way?
If the answer is no...
Why am I getting a false row count?
Thanks in advance.
