ScottRobertson
6 years agoQrew Trainee
When to use Automation vs. Form Rule to modify a field value
I have reviewed all the standard documentation around Automation within University.QuickBase.com and Help.QuickBase.com, but cannot find a rule of thumb for when you should use Automation vs. a Form Rule when attempting to change field values.
Is the only difference that an Automation will only fire once the record is saved and a form rule can perform actions "live" while editing a record? I'm running into the "40 Derived Field Limit" within my Form Rules and before totally restructure my fields/formulas/logic to avoid using a derived field, I'd like to understand if this is something an Automation could help with.
My Specific Example (I have 40+ different "due date" fields)
1. When a checkbox changes from unchecked to checked
2. Change a date field to be 3 business days from today's date (the actual rule is Change "Due Date" to the value in the field "Due Date Formula" field = WeekdayAdd(Today(),3)
Thanks!
Is the only difference that an Automation will only fire once the record is saved and a form rule can perform actions "live" while editing a record? I'm running into the "40 Derived Field Limit" within my Form Rules and before totally restructure my fields/formulas/logic to avoid using a derived field, I'd like to understand if this is something an Automation could help with.
My Specific Example (I have 40+ different "due date" fields)
1. When a checkbox changes from unchecked to checked
2. Change a date field to be 3 business days from today's date (the actual rule is Change "Due Date" to the value in the field "Due Date Formula" field = WeekdayAdd(Today(),3)
Thanks!