Question
IBM India Pvt. Ltd.
IN
Last activity: 5 Aug 2016 16:14 EDT
how to import the archived Work objects created through "Purge and Archive Wizard" into a different system where same WO ID already exists ?
Say I have created a archive from the purge and archival wizard from system A, this archive contains some set of Workobjects with ID's say WO-23, WO-24. I am trying to import this archive into system B where there is already some WO exists with same ID . I tried this and saw the import wizard in system B is showing a warning message for same ID's.
But my question is- we have requirement to do this, how to handle such scenarios. ? Is it possible to change the WO ID's of archived WO's from system A ?
***Updated by moderator: Lochan - User still needing assistance. Adding #helpme tag***
Accepted Solution
Pegasystems Inc.
IN
IBM India Pvt. Ltd.
IN
Still looking for help.
Pegasystems Inc.
IN
we will run into primary key violations issues [pzInskey already exists...]
Pegasystems Inc.
IN
also perform a test import on sandbox to observe the SQL statement if it is generating insert or merge statements.
insert: will throw error
merge: overwrites the instance
how to handle...(not sure, but)
need to obj-open-by-handle of the workobjects and change the ID prefix atleast.
IBM India Pvt. Ltd.
IN
still looking for some help on this ? any suggestions ?
Accepted Solution
Pegasystems Inc.
IN
Hi.
i tried it at my end . In my test system I packaged my work and then tried to import the same package in the same system. I found that it is throwing the same warning that you get when you have the same name rule in your application while importing a rule. So you end up with two choices. Either skip or replace. And none for your case will work.
Tried obj open by handle but that seems to be not solving the purpose. I cant actually find any alternate option available. We need to take it as an enhancement.
Others can comment.
IBM India Pvt. Ltd.
IN
Thank You Santanu.
Hi.
i tried it at my end . In my test system I packaged my work and then tried to import the same package in the same system. I found that it is throwing the same warning that you get when you have the same name rule in your application while importing a rule. So you end up with two choices. Either skip or replace. And none for your case will work.
Tried obj open by handle but that seems to be not solving the purpose. I cant actually find any alternate option available. We need to take it as an enhancement.
Others can comment.