Master to Detail Records - Quicker way to do this?
Is there a quicker way to create child records than having to press the button or importing a spreadsheet?
Forum Discussion
I am not sure you want a "quicker:" way to add child data or a way that has fewer navigation steps. But in any case it all boils down to where the data is coming from. Consider the variety of ways data could be used create child records:
(1) perhaps the child records are created using default data. Example: create 12 child records one for each month in the next year
(2) perhaps the child records are created using an input solicited from a dialog box. Example: display a dialog asking for the number of child records to create (and perhaps other user inputs)
(3) perhaps the child records are created based on a records in a related table used as a template. Example: create child records by copying records from a related table
(4) perhaps the child records are created by parsing a selected file. Example: invite the user to select a file, parse and transform the file's contents and they add the generated records to the child table.
(5) perhaps the child records are created by scraping a web page identified by URL. Example: grabbing prices, addresses or other data from an external web site.
(6) perhaps the child records are created by accessing and parsing data currently in the clipboard. Example, a user selects a table of data for a web site and pastes the data into a QuickBase form which parses and transforms the data before slotting the data into fields.
All of these scenarios are possible with script. So I would invite you to refine the source of the data and where you want it to land in QuickBasae.
(1) perhaps the child records are created using default data. Example: create 12 child records one for each month in the next year
(2) perhaps the child records are created using an input solicited from a dialog box. Example: display a dialog asking for the number of child records to create (and perhaps other user inputs)
(3) perhaps the child records are created based on a records in a related table used as a template. Example: create child records by copying records from a related table
(4) perhaps the child records are created by parsing a selected file. Example: invite the user to select a file, parse and transform the file's contents and they add the generated records to the child table.
(5) perhaps the child records are created by scraping a web page identified by URL. Example: grabbing prices, addresses or other data from an external web site.
(6) perhaps the child records are created by accessing and parsing data currently in the clipboard. Example, a user selects a table of data for a web site and pastes the data into a QuickBase form which parses and transforms the data before slotting the data into fields.
All of these scenarios are possible with script. So I would invite you to refine the source of the data and where you want it to land in QuickBasae.