For dynamic model with strategy ‘Staged’ it is important that everything that is connected, is in the same control procedure code field so that if something is removed from the model by the dynamic code, it is cleaned up without any errors. 

The result is dynamic model with many lines of code in one field that does multiple things. An example is the meta_view_history from the Thinkstore (Logging data available in the GUI), there is code for creating views, creating view columns, detail tabs, conditional layout and setting up roles all in one field. 

I think it would be an improvement if dynamic code control procedures could be separated into multiple code fields to be able to structure the code. This would make it a lot easier for maintenance. 

A possible way for doing this could be by adding the template level for dynamic model control procedures.