I’m working on a project where up to 20 concurrent users enter data into a shared table, either line-by-line or via copy-paste. This data is then submitted to another document through webhooks and automations. Each user only sees and submits their own records, filtered by User().
To indicate data validity, I’m using an “inverted” conditional formatting model: cells are red until the data is correct. This works well for guiding users in real-time, but as the number of records grows (50+ or sometimes hundreds), performance suffers—particularly when clearing red formatting as data becomes valid.
I’ve tried trimming the table by archiving or deleting submitted records, but some users may leave records unsubmitted while gathering more information, which tends to keep things sluggish.
Any advice on improving the performance and elegance of this process would be greatly appreciated.
Hi,
There is a YouTube video from TheCodaGuy discussing conditional formatting and best practices.
I saw that you have 12 rules for conditional formatting. Instead of having those formulas there, what if you created checkbox columns in the table for each formula and then a master/summary checkbox column that checks if those individual columns are all true? Then, in the conditional format menu, you would have 1 rule tied to the master checkbox result.