Forum Discussion
QuickBaseCoachD
7 years agoQrew Captain
A form rule take zero resources as it runs in the browser and it has the advantage of only being smart enough to act on the record on your screen in human edit mode.
The Automation has the "disadvantage" of being more powerful and having to run after the record is saved, so then it has to scan all the records in your table to locate the one to be edited.
But you can use both, as what will happen is that you will only trigger the Automation when the record is added or modified and those two fields don't match. 99% of the time they will match (because of the form rule) and it will not fire. (but in Grid Edit mode, Forms rules do not apply, so then the Automation will kick in).
Be sure on the form rule to un-check that box at the bottom to make sure it always fires when the fields do not match.
The Automation has the "disadvantage" of being more powerful and having to run after the record is saved, so then it has to scan all the records in your table to locate the one to be edited.
But you can use both, as what will happen is that you will only trigger the Automation when the record is added or modified and those two fields don't match. 99% of the time they will match (because of the form rule) and it will not fire. (but in Grid Edit mode, Forms rules do not apply, so then the Automation will kick in).
Be sure on the form rule to un-check that box at the bottom to make sure it always fires when the fields do not match.