We have tried to use the Update Family Campus Data Automation Job, but have found that we have too many "exceptions" (people that should NOT have their campus changed even though they technically meet the requirements that would update their campus) to make it useable. Situations like a Staff person attending Campus A, but their job necessitates they regularly check into groups at Campus B... the job eventually moves such people to Campus B when they shouldn't be.

We'd like to see an option for  The person is not in the following dataview  added to this job, just like the Reactivate/Inactivate jobs already have. This would allow us to control/prevent staff (or any other edge cases) from having their campus switched when it should not be.