How should you structure the process model to add new invoice and the new invoice items to the system?

How should you structure the process model to add new invoice and the new invoice items to the system?

• A. Script Task to update foreign keys; Write to ACME_invoice; Write to ACME_Invoiceitem.
• B. Write to ACME_invoice; Script Task to update foreign keys; Write to ACME_Invoiceitem.
• C. Write to ACME_invoice; Write to ACME_Invoiceitem; Script Task to update foreign keys.
• D. Script Task to update foreign keys; Write to ACME_Invoiceitem; Write to ACME_invoice.

Answer: (B)

The sequence starts from the need to have a valid parent key before creating the related child records. Create the invoice first so you obtain its primary key. Then use a Script Task to populate the foreign key on each invoice item with that newly created invoice's ID. Finally, write the invoice items themselves, now that their foreign key correctly references the parent invoice. This order ensures referential integrity: the child rows can always point to an existing parent, and you avoid inserting children with missing or incorrect foreign keys.

The sequence starts from the need to have a valid parent key before creating the related child records. Create the invoice first so you obtain its primary key. Then use a Script Task to populate the foreign key on each invoice item with that newly created invoice's ID. Finally, write the invoice items themselves, now that their foreign key correctly references the parent invoice. This order ensures referential integrity: the child rows can always point to an existing parent, and you avoid inserting children with missing or incorrect foreign keys.