PC_DATA_UNIQUEID primary key violation in pega
Hello Everyone
We have more than one application, we do both migration and upgrade, currently in the process of migrating the data, we are getting primary key violation when we migrating data into PC_DATA_UNIQUEID.
PC_DATA_UNIQUEID table (pzinskey) contains class and pyprefix as a primary key. Both source and destination have same primary and different values for column PYLASTRESERVEDID .
Eg. DATA-UNIQUEID !PM- record contains both source and the target for pzinskey but other column PYLASTRESERVEDID contain different values.
I wanted to know do we have any possible work around to keep both record in target.
Can we update PYLASTRESERVEDID to some value where it works for both the applications?
Thanks
***Edited by Moderator Marije to change Type from Discussion to Question***