Forum Discussion
QuickBaseCoachD
Qrew Captain
What I did once in that situation was to detect if the Parent had at least two future children tasks.
I set up a saved table to table import to copy the parent into the child task table and populate the task due date field as the parent would know the frequency of the task and the most future task created so far.
Then I set up an automation to import the parents who did not have at least two next future dated into a child table to create the next Child Tasks for all parents. I ran the imports twice each day in the same automation.
So that way each night after midnight, I would know that each parent had at least 2 future tasks.
I set up a saved table to table import to copy the parent into the child task table and populate the task due date field as the parent would know the frequency of the task and the most future task created so far.
Then I set up an automation to import the parents who did not have at least two next future dated into a child table to create the next Child Tasks for all parents. I ran the imports twice each day in the same automation.
So that way each night after midnight, I would know that each parent had at least 2 future tasks.
QuickBaseCoachD
5 years agoQrew Captain
... hence the saved table to table copy. I only copy Parents into the child table to create a future task if the Parent does not have two future children.
So the Automation will always run, but the saved table to table import may result in no records being created, certain no records being created for most parents, most days. But some parents will run low on future children and hence be valid for the saved table to table copy filter and "give birth".
So the Automation will always run, but the saved table to table import may result in no records being created, certain no records being created for most parents, most days. But some parents will run low on future children and hence be valid for the saved table to table copy filter and "give birth".