Let’s say I am searching for an app with 2,000 records and am looking for the 1,500th one. Will the Search for Record Automation not see it (since the limit is a thousand)?
Usually, I use the 🆕 Action · Filter collected · Workflow Automation because it gives me more flexibility to filter the search. However, if the search automation only sees the first thousand, will the filter work for all the records in the app?
Tape can store up to 500,000 records per app. Does the “search for records” search all or only the first thousand?
@Luis just to play Devil’s advocate here, wouldn’t it make more sense to do a filtered search at the outset? One of my favourite features of Tape over Podio is that I can search by more than one parameter (find items where x = y AND y = z, etc.)
I know you can filter collected records after the fact, but wouldn’t it make more sense to get as close to the records you’re looking for in the initial search, rather than filtering them after the fact? Both Podio and Tape’s API can only return 500/1000 records at a time; not only is that not going to change for common sense reasons, but gathering more records than you need will always slow things down.
Search would apply to ALL records in an app, but would only return the first 1000 results depending on how they’re sorted. I think that “created on, descending” is the default sorting mechanism.
That is a good point. If the search filter is straightforward, I can usually filter it directly in the “search for records automation” filter. The problem is that this filter does not have the “add filter group” option or the "Or" operator (it only allows "and").
Not having that limits the filtering, especially when filtering dates. The filter for collected records enables more flexibility, but it would be fantastic if the “search for records automation” had the filter groups and “or”.
