We are on Pega 7.1.8 and we are noticing that we have a number of records in our declare index table with pxIndexCount = 0. Normally, the indexing should start with 1. Was this some issue which was addressed? Is it safe to manually cleanup the table where pxIndexCount = 0? The data indicates that we have duplicate rows for the same inskey, only difference is the pxIndexCount value.
We have also applied the following hotfixes:
HFIX-28859Diagnostic: Declare index doesnot fire everytime as expected
HFIX-29212Declare index doesnot fire everytime as expected
HFIX-30442deferred save failing in RecalculateAndSave
HFIX-33049Reindex count and pzindexes are not getting updated
***Edited by Moderator Marissa to update categories***
The pxIndexCount property makes each row unique. This property is zero-based; the first (oldest) index instance has a pxIndexCount of 0. The pxIndexPurpose key part identifies the Declare Index rule that created the index.
For more information please refer below pdn document.