Hi!

ok, this is how we do it now.

At task level add the new release.

in the same task, we creates an new object in the new application with same name and attribute as the old one, then it is in dvp.

then we checkout from the old app to dvp. 
after that we promote the source/object to the new application.

Now we can cleanup the old application.

../Å

It's a way, although I think the process takes longer, and all objects are registered as new.
The procedure I'm describing avoids adding a task and promoting to PDN.
The steps are:
1) Keep the sources and objects in a temporary library.
2) Go to option 13 = Work with Releases, locate the new application, then select option 9 = Populate, then option 3 = Load release.
3) Once loaded, remove it from the old application.

Best Regards,

Yasmely Henriquez

Hi - the solution provided by Yasmely is an acceptable approach but I always like to know the what and why of requests like this. Is this just for 1 object or multiple objects? How come you have objects in 1 application that should really be in another application?

Don't forget if you use the Load function you're pushing code directly into the Production environment in RDOi without doing any testing on it. Also, for example, if you move a PF in this way, don't forget any associated dependents (LFs, *INDEX, *VIEW).

Regards,

Donn Broadbridge

Principal CSE Delivery Engineer