Forum Discussion
AndrewFry
5 years agoQrew Assistant Captain
Mark,
That is an interesting way to have it do it. Basically you just mass produce in bulk, then remove the copies you don't need. The removal is going to be the difference between the # mass produced (in your example it was 20) and the number desired.
I will have to give that a try. Thanks Mark!
------------------------------
Andrew
andrew.fry25@gmail.com
------------------------------
That is an interesting way to have it do it. Basically you just mass produce in bulk, then remove the copies you don't need. The removal is going to be the difference between the # mass produced (in your example it was 20) and the number desired.
I will have to give that a try. Thanks Mark!
------------------------------
Andrew
andrew.fry25@gmail.com
------------------------------
MarkShnier__You
Qrew Legend
5 years agoThe delete would be on any value 1-20 written onto the child which is higher than the lookup of the number required.
The number required will be looked up down to children.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- AndrewFry5 years agoQrew Assistant CaptainSo I have decided to try the looping method for the time being. But I think I hit a snag.
Basically I create the Parent record and at the same time I create a child record.
I then need to copy the Parent/child pair, X number of times the user needs.
Copying the Parent record has proven to not be too difficult. The issue I am facing is properly copying the original child record, and associating it to the copied parent record. I won't know what the copied parent record ID # will be ahead of time so ......
I wonder if I need to run a separate automation for the child records, and have some sort of trigger field in the copied parent record to do it ..... ????
Also, Mark, would you method of mass producing records work with copying child records too? I kind of steered away from doing the mass record creation because I have some automation in place to generate notes when various records are created. I would hate to have 20+ notes for deleted records that were not actually needed.
------------------------------
Andrew
andrew.fry25@gmail.com
------------------------------- MarkShnier__You5 years ago
Qrew Legend
I had assumed incorrectly that you wanted to create X number of child records for a parent. But now i see that you want to duplicate the parents and now want to add a wrinkle that these copied parents need to be born with children too.
Are the children to be created always the same, or do they need to take their values for some data from the original Parent's children.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- AndrewFry5 years agoQrew Assistant CaptainThe copied children need to mirror the original child.
I have set up templates for both the Parent and Child records before, but those are consistent across the board.
I would imagine this is something similar, but there is the facet of the child data being different each time.
Hopefully that makes sense.
------------------------------
Andrew
andrew.fry25@gmail.com
------------------------------