Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article




When upgrading to PegaCRM_731, PYLASTRESERVEDID value in table PC_DATA_UNIQUEID is overwritten for a number of object IDs.

For example,

In Pega Sales Automation 7.31, the PYLASTRESERVEDID counter in Table PC_DATA_UNIQUEID is reset to 10.
After the upgrade, the counter for Business Territories (BT) previously set to 15990, is reset to 1002.
This counter or sequence number is used every time a new object is created for the Unique ID (Value of PYLASTRESERVEDID + 1).

The PegaCRM_731.jar (standard installation package for Sales Automation) contains instances of Data-UniqueID.

Error Messages

Not Applicable

Steps to Reproduce

Deploy Pega Customer Relationship Manager (CRM) or Sales Automation 7.31 upgrade on a used system. Verify PC_DATA_UNIQUEID instance values (both pre and post upgrade deployment).

Root Cause

The PYLASTRESERVEDID values in the PC_DATA_UNIQUEID table, for a number of impacted object IDs, were incorrect.


Perform the following local-change restore system operation:

Manually reset PYLASTRESERVEDID values in the PC_DATA_UNIQUEID table for a number of impacted object IDs to the correct values for the corresponding objects.


Published February 12, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us