Forum Discussion
MarkShnier__You
Qrew Legend
5 years agoThere are multiple solutions. What is the most # of records you would possibly need to create as that would affect my suggested solution..
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- JoshuaCase5 years agoQrew CadetLet's say at worst 29.
------------------------------
Joshua Case
------------------------------- MarkShnier__You5 years ago
Qrew Legend
The low tech solution would be to have an Automation to create 30 or if you like 49 children. Each Action in the Automation will populate a field with the child number, from 1 to 30. You can copy Actions, so it's not too painful to set up.
Then lookup the # children required from, the parent to the children, and add a last step to delete children when their counter # is greater than the # of children required.
There are fancier methods which are a bit harder to setup which would have a better user experience as the children would get created quicker, but this low tech method could be good enough.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- JoshuaCase5 years agoQrew CadetAny way to describe the fancier method? The example you provided is good and can be done quickly but I need to create the most streamlined experience for the end-users that's most effective and delivers the exact number of child records based on the parent's data. I like a challenge and I don't mind a difficult setup.
------------------------------
Joshua Case
------------------------------