Create Multiple Records from Find Records Result
After executing a "Find Record" automation action, create a record for each of the found records with a script
View the solution base hereBase Details
Salestable- Each record contains the following information for the sale:
- Serial number
- Date of sale
- Line Items
- Each record contains the following information for the sale:
Line Itemstable- Each record contains the following information for the line item:
- A link to its parent
Salerecord - A link to the
Productrecord that is being sold - The quantity of the product that is being sold
- Links to the relevant
Pick Listrecords
- A link to its parent
- Each record contains the following information for the line item:
Productstable- Each record contains the composition details of the product:
- Links to the parts that it is composed of
- Links to the relevant
Line Itemrecords
- Each record contains the composition details of the product:
Partstable- Each record contains the following information for the part:
- A link to its parent
Productrecord - The required quantity for this part
- A link to its parent
- Each record contains the following information for the part:
Pick Listtable- Displays all of the parts that need to be picked, as well as how many of each part to pick
- Displays all of the parts that need to be picked, as well as how many of each part to pick
Scope
The client was using a "Find Record" action in an automation to identify the specific product components they needed to pack.
This worked fine and they were able to successfully find the product component records they needed.
After that, they needed each of these records to be created as a new record in a table that was formatted specifically for packing.
The Solution
We utilized a script that would take in the results of the "Find Record" action, and for each of them, create a new record in the appropriate table with the data the client needed.
"
I cannot thank Adam enough.
We had a business problem that required a piece of script to be written to solve. This was outside of my knowledge and I posted on the Airtable community forums with my problem.
Adam reached out with a solution which was very close to being perfect (it was from my lack of detail that it wasn’t).
He personally reached back out to see how everything was going and I mentioned it wasn’t quite right, he kept working with me (he even jumped on a call and ran me through how the input variables work) until we found the correct solution all on his own time!
Thank you Adam, we really appreciate your work!