That’s a great wizard use case.  But these things get really complicated…

This is what I think needs to happen:

On Create another child record run the following action sequence. 

1. Save parent
2. Save child 1
3. Empty rows on the child model
4. Create new row on child model.   I think the condition will pre-populate the data with the right parent ID.  You’ll want to check this tho. 
5. Go back to the child definition step of the wizard. 

I think that should do what you are looking for. 

---

Sorry to resurface this one - but I’m trying to do something kind of similar. I want to use a wizard to:

Step 1: create a parent record (expense report) and then move on to
Step 2: a table that allows the user to create child records (expense line items). I don’t have a ton of experience with action sequences - so I’m a little stumped on how to get started. Are there any tutorials or other posts with explanations or xml I could copy and use as a reference?

---

Kaede,

I don’t think you need to use the action sequence. Just make sure to set a condition on your expense report lookup field on your expense line item record to the Id of the model of your expense report. Skuid will take care of setting the right ‘Id’ when you save the expense line item model.

Here is an example page that shows this. You can create a ‘parent’ account and ‘child’ contacts. It uses a 2 step wizard. As an alternative, you can also have a single page that shows the expense report fields at the top and a table to allow entry of child expense line items.

Thanks,

Bill

Account
Contact

---

This is perfect - so helpful. Thank you!!!

---