I suggest that you consider not using Pipelines or Automations to individually add the parts list.
Instead, make a table of Standard House types - in fact maybe you already have this table which would select from when you create an Activity. Create a child table to that table called Standard Build Parts. The standard build parts would be selected off a relationship from the Parts Master.
The set up a pipeline to trigger when a House Type is selected and the Activity has no child build parts as yet.
The Pipeline will trigger and the search the Standard Build parts table for those parts which match the House Type. Then have a "For Each" loop to create the child Build parts records.
The advantage of this method, of course, is that you can easily maintain the standard build parts for any Standard House Type, the Standard Build Parts are easily visible to users, and creating new House Type with their own sets of standard bill parts is easy without having to modify the Pipeline.
------------------------------
Mark Shnier (Your Quickbase Coach)
[email protected]------------------------------