Moving an entity to another espace without loosing their data

By lef on 10 May 2010
when refactoring entities between espaces, manual database scripts are required to migrate data to the new physical entity
Nuno Fernandes14 May 2010
Hi,

Moving one entity from one eSpace to another one and  keep table name and table data is an important feature to have in Outsystems.

We had this issue when we started doing eSpace refactory and need to have entities associated with another eSpaces without changing physical table name.

For example in eSpace X we have CLIENT and POLICY entities and we created two eSpaces with these themes (clients and policies). In Policy eSpace we need POLICY entity and in Client eSpace we need CLIENT entity...

Best Regards,
Nuno Fernandes


Merged from 'Move Entity to another eSpace' (idea created on 14 May (3 days ago) by Nuno Fernandes), on 11:06 (just now) by Pedro Oliveira
J.15 May 2010

similar to http://www.outsystems.com/wisdomofthecrowds/IdeaComment_List.aspx?IdeaId=72


Merged from 'Move Entity to another eSpace' (idea created on 14 May (3 days ago) by Nuno Fernandes), on 11:06 (just now) by Pedro Oliveira
Joop Stringer3 Dec 2012
I got a message that this is possible to do by going into the database and switch eSpace ID's in the meta model.

Only have to figure out how it actually can be done :-)
Kilian Hekhuis13 Mar 2015
We've managed to this by copying the table in Service Studio to the desired eSpace, publishing that, then going to the database, delete the new table and rename the old table to the new one. But yeah, it'd be vastly superior to be able to do it from Service Studio.