For our current customer we only use Snapshot-Packages with Replace Action.
Especially DDL-Packages should get deployed as soon as possible, in the order of their creation.
For example:
WORKORDER object has ATTR1.
1. Package adds attribte ATTR2 to WORKORDER.
2. Package deletes attribute ATTR1 to WORKORDER.
If you now deploy package 2 before package 1, the WORKORDER Object will still have ATTR1 as it is part of package 1.
So the last one wins.
Hope that helps.
------------------------------
Jens Schmeiser
Service Management Consultant
scienITec GmbH
Munich
------------------------------
Original Message:
Sent: Mon March 23, 2020 10:59 PM
From: MANU MAGANTI
Subject: Delete object attributes using Migration Manager
Thanks for the reply! It looks like Replace action does do it on a Snapshot package. I wasn't sure if that would have unexpected results. Any experience with that?
------------------------------
MANU MAGANTI
EMA Canada| Inc.
OAKVILLE ON
------------------------------
Original Message:
Sent: Mon March 23, 2020 12:17 PM
From: Jens Schmeiser
Subject: Delete object attributes using Migration Manager
If you already deleted the attributes from the object, create a package definition of type SNAPSHOT (https://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.1.1/com.ibm.mbs.doc/gp_migmgr/c_snapshot_pkg_definition.html).
This will create a package of the object as it is right now, and should delete the attributes in your target environment which are not part of the package.
------------------------------
Jens Schmeiser
Service Management Consultant
scienITec GmbH
Munich