Moving an entity to another espace without loosing their data

On our radar
when refactoring entities between espaces, manual database scripts are required to migrate data to the new physical entity
Created on 10 May 2010
Comments (13)
14 May 2010

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
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 Stringer
3 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 :-)
13 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.

Refactoring tooling.....!!!!!

28 Jul 2017

This continues to be really relevant!

28 Jul 2017

It absolutely does.

26 Aug 2017

Great idea, especially when you want to split out functionality and use it as a shared component.

Yes, this feature is useful especially refactoring the code

10 Nov 2017


There is ANY reason (besides other priorities) to this to not have being implemented as part of the platform yet?
Move entities from one module to other is absolute essential when doing refactoring, and it poses lots of problems...

Anything other than change metadata information is required in order to do this?

11 Nov 2017

Agreed. The refactor forge component is a waste to use. Its not helping really because you need to do roughly the same amount of work.

Refactoring means better quality for the developers and customers because you can create more seperate apps...

27 Nov 2017

Sounds like we're all on the same page. I know the ability to drag and drop an entity exists, but no data transfers. That's the real need: move an entity with data from one module or eSpace to another. Is it possible to do that from the SQL backend?

We really need this...