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

Conflicts display while merging ruleset despite no rule changes



Conflicts display while merging a ruleset even when the rules do not have changes.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Save as a rule to the branch ruleset
  2. Merge the branch and observe that conflicts display

Root Cause

The time stamp pxUpdateDateTime is different in the exposed column and BLOB column. In the exposed column, milliseconds are truncated and set to 000 whereas the BLOB column has the correct milliseconds value. As the time stamp is different, during comparison of the rule data in the merge wizard, conflicts display as the timestamp does not match.


Perform the following local-change:

Run the column population to resave the values from the BLOB column for pxUpdatedatetime column in the data-rule-summary class with the below parameters set in the file:
  • expose.classes.included=Rule
  • expose.included.descendent=true 
  • expose.reindex=false 
  • expose.update.rule.summary=true 
  • expose.reindexType=full 

Published October 27, 2018 - 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