Hi All,

I have configured a non-repeatable work-party in my case type. When the work-party is added and work-object is committed to DB, I can see "pxIndexCount" set as "0" in Index-WorkPartyUri table by Pega. 

I am migrating this work-object to other environment using RAP file. After the RAP is imported, I can see that "pxIndexCount" set as "1" by Pega. Pega GCS Team says it is expected behavior. 

The user is making a change to the work-object and committing in the first environment. The changed content is exposed in the partyURI declare Index rule and in the DB table in both the environments. I can see that the changed content is reflected in the DB table in the first environment in the existing record where "pxIndexCount" is "0". Now, we're trying to sync this case to 2nd environment using custom REST API calls. During this API call service activity, when the case is committed to DB in second environment, Pega is inserting a new record in the Index-WorkPartyUri DB table. PFA doc with screenshots highlighting the same.

Now the user is reporting a defect saying that the case is displayed twice. As the report is fetched based on the Party Role, 2 records created above are displayed in the UI. 

Need help to understand what is that I can do to fix this issue. I have looked in the below posts on the similar subject but they are all closed. Hence, raising this one.

Duplicate Rows in Index Table | Collaboration Center (pega.com)

How to eliminate duplicate work party | Collaboration Center (pega.com)

Declare index created duplicate records for old work-object save when code promoted to other env. | Collaboration Center (pega.com)

Regards

Giridhar Metikal