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

Declare Index out of sync



The user's work item PageList properties are out of sync with the associated DeclaredIndex table. MSome work items can have more PageList items in the blob than the row counts in DeclareIndex table. Some other work items can have fewer PageList items in blob than the row counts in DeclareIndex table.

The application creates work items via an import process. These PageList items are maintained by the import application using the OOTB methods. What it does is: 

-When an itemA, itemB or itemC is inserted, we do a Page-New on itemA_PL, itemB_PL or itemC_PL respectively. Then we set properties on the last page of this page list. 

-When an itemA, itemB or itemC is is updated, we find the index of the affected page by calling the IndexInPageListWhen() function. Then we set properties on the page with this index. 

-When an itemA, itemB or itemC is is deleted, we find the index of the affected page by calling IndexInPageList(). Then we delete this page with this index. 

Error Messages

Not Applicable.

Steps to Reproduce

  1. Create a work class that contains a pagelist property.
  2. Create a Declare Index on this pagelist property
  3. Create a few instances and perform a huge number of updates, inserts and deletes on this pagelist properties of those instances
  4. Compare number of pages in the pagelist properties with number of corresponding rows in declare index tables.

Root Cause

An issue in the custom application code or rules.


The generated code by using Page-New with .PageListName(<APPEND>) as step page has .PageListName(<APPEND>) multiple times. Suspecting this implementation its adding more than one elements to the list which is undesired. Proposed to avoid use of Page-New and directly use .PageListName(<APPEND>) first and then use .PageListName(<LAST>) to access the data in subsequent steps if required. Since the local change has applied, the reported issue has not occurred.
Suggest Edit

Published June 30, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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