For the Electoral API extension, I want to write a scheduled job to look up legislative data for everyone who a) has a geocode, and b) doesn't already have legislative data (which is stored in a multi-record custom field). I need this to be scalable.
So I could look up every contact without legislative data, then check those contacts for geocodes, or vice versa. Either way, I'm checking a huge number of contacts for data. Is there a better way? Maybe using API chaining?
Is it possible to create a smart group that's hidden from the UI that meets these criteria, then use that as the basis for my scheduled job? That seems like the best option.