How does the ordering/lifecycle work with dependencies within the templates?

[pmatthews05]

Could someone point me to the code where when a provisioning template is provided, and the code know which to provision first, and how it goes back to something, because it cannot complete the creation without creating something else first.

For example, if I need to create Site Lookup Column that points to a list (which is also required to be created). A content type that holds the Site lookup Column, and a second list with this content type that contains the Site Lookup Column that points to the first list.

I'm just curious how this works. If there is a YouTube video that explains this, please just point me to that. (I couldn't find one.)

[gszdev]

@pmatthews05

see

• // 1st. create fields, content and list without lookup fields
• // 2nd. create lookup fields (which requires lists to be present
• ...