Forum Discussion
_anomDiebolt_
7 years agoQrew Elite
Don't use Automations - just use a simple native formula (with some embedded JavaScirpt)! If you use 100 looping Automations QuickBase will run low on inventory and everyone will be effected.
Without loss of generality, I am going to assume you want to create N child records associated with a parent record you are viewing.
Here is the demo:
Create N Child Records ~ View Parent Record
https://haversineconsulting.quickbase.com/db/bn8aam6y8?a=dr&rid=1
Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=td&rid=698
Notes:
(1) Feel free to create your own parent record and add your child records to it by viewing the parent record and clicking the button.
(2) You can customize the formula further by editing some of the hardcoded ids and apptoken,
(3) No code pages was used in the creation of this demo.
(4) This is a great way to initialize child records representing a number of fixed assets such as seats in a class,
Without loss of generality, I am going to assume you want to create N child records associated with a parent record you are viewing.
Here is the demo:
Create N Child Records ~ View Parent Record
https://haversineconsulting.quickbase.com/db/bn8aam6y8?a=dr&rid=1
Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=td&rid=698
Notes:
(1) Feel free to create your own parent record and add your child records to it by viewing the parent record and clicking the button.
(2) You can customize the formula further by editing some of the hardcoded ids and apptoken,
(3) No code pages was used in the creation of this demo.
(4) This is a great way to initialize child records representing a number of fixed assets such as seats in a class,
- AustinHayes7 years agoQrew CadetI will look into this as an alternative to the loop. I'm not concerned about having a single looping automation in my app.