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

Data table duplicate entries while migrating code



User has two environments, development and QA. User deployed an application consisting of data table and its instances from development to QA using Rule-Admin-Product (RAP).
Later in development environment, user has built more features and added few entries to data table and modified existing entries.
Now user is in the process of building RAP for that delta. After RAP is created, further modified the RAP to create a 'select query' to select only specific instances of data table and deployed into QA.

Now observing that instead of updating the existing entries in data table, it is creating duplicate entries for updated records.
User does not have the log files on the day RAP was deployed.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Create Datatable with some entries in it. Let's assume TableName is TestTable.
  2. Create R-A-P in dev environment and import it to QA.
  3. Add one more record to the TestTable in which Primary key column name is Label(Label=11).
  4. Create R-A-P to include newly created record(Label=11) and imported it to QA environment again.
  5. Now records in QA env would be 11 records. We can see 11 records as expected.
  6. Modify the values of some column other than primary key of 11th record in dev(Still Label=11). Let's say change the value from A to B. Refer step8.
  7. Repeat step4. Now records should be 11 as Primary key will be the same as user modified the value of different column than Primary key column. However when user imports the new R-A-P to QA environment one can see 12 records present in TestTable data table instead of 11 records.
  8. Label    Name
          11          A    Old one
          11          B    Changed one
  1. If  user removes one record which contains(Label=11) both the records are getting deleted.

Root Cause

A defect or configuration issue in the operating environment.

Data table used to create export and import does not have primary key defined in the mentioned table.


Update the pzinskey as primary key instead of Label which resolves the issue.

Published January 31, 2016 - 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