Complex Worklfows and Filtering Limits

[Kristo]

Hey there Gliders,

i am currently trying to build Glide App that helps my Team to track Expenses against their current Projects.

User and Projects are N:N whereas Projects to Expenses are 1:N Relations.
The challenge here is that Receipts and Projects are multi currency. I got the conversion covered via API call when they are created. Easy bit …

But now I am just covering for the case when the Admin requires to change the Project Currency when already Receipts are linked. Therefore i would need to check which Receipts need a new conversion rate (a.k.a new API call)

I think i got that sorted as well with triggering a Webhook on UserAction that will pass on a JSON and trigger a Loop Flow.

What i am trying to understand is how the “Filter Function works” as it is limited to 1000 rows. the question here is :
How do I correctly filter the data to avoid hitting that limit. As i have in the same table many receipts and i dont really need the loop to run through all of the receipts only the ones that were associated with the Project. hence the Filter.

I figured two ways to set it up first one is by adding a “computed Query” prefiltering the Table and the using that data within the Loop Flow.

Is the “computed Query” Limited by the amount of Rows in source table it is querying ? and what’s the limit the Result it can contain ? On the latter question I am sure i wont exceed 200 Receipts per Project, so i presume that should be safe then!

But i also saw that you can set a filter directly in the Loop settings.

Whats the difference in either scenario ?

[ThinhDinh]

@Kristo

Is the “computed Query” Limited by the amount of Rows in source table it is querying ?

I’m not quite sure if there’s a limit at all on the rows that are in consideration, I think the advice I got is not to loop through more than 1000 rows.

[Kristo]

Great thanks for the reply. I doubt that i will loop through more than 1000.
hence i wanted to pre-filter the data before running the loop.

is there a difference if i set the Filter directly in the loop or if i do a “computed query” with the filter applied before using that data in the loop.

[Darren_Murphy]

@Kristo

is there a difference if i set the Filter directly in the loop or if i do a “computed query” with the filter applied before using that data in the loop.

No difference that I am aware of. One reason why you might use a computed query in preference is that you might use it for other purposes within the workflow.