Among thousands of records, if we are trying to update a random subset (i.e. status or date complete, etc.), is there a way to do that without searching one by one and updating one by one?
I'm imagining the ability to type in comma separated project numbers that would list the results (or missing result in case they type the wrong number), and then the ability to update one or more fields for those records.
In the event users are typing in 50 or more jobs and accidentally fat finger a project number that isn't listed, is there a way to flag that situation? It's not uncommon for us to update 300 projects at once with a complete status. Unfortunately, these are all random job numbers.
As for supporting all types of boolean searches, well I don't think that you can nest the conditions with brackets in that search box, but it supports AND in upper case and OR in upper case and I forget offhand which one dominates when you say
ACTIVE AND 1234 OR 2345
If you want a more robust method which will detect bad numbers, one question is if the source of these "300" projects can be coaxed to create the OR string. For example an Excel formula if that was the source or in fact a QuickBase formula - ie what is the source of knowing those 300 Project numbers?
I can think of other more robust solution to detect non hits. For example if you had a new table of Projects to be Updated and imported in or grid edit typed in those "300" project numbers. That Project # field could be set as the key field to that temporary list of Projects to be updated. Then via a relationship, that would light up Projects in the real projects table which have entries in the projects to be updated table. Then you do your mass update.
The Projects to be updated table can flag in colour of the Parent Project to be updated has no Project Children, ie you typed 123X5 and there was no project with that number.
When you are done with updating you purge the records in that temporary table with a URL formula button.