@albertca I do not think, that the approach of embedding the migration logic inside module would work, because fields are dependent on each other (think of onchange event), and those may change as well. So it is possible to create the script or scenario manually.
The other thing to consider: in many cases enterprise want to add some modules in addition to those which was in the legacy setup. Think of module X, which adds mandatory field ABC (which has no default values) to a model created by other module. What if that module X was not present in legacy setup, but needs to be used on a new one? Kaspars ------------------------- http://kndati.lv -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=61332#61332 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
