Support Article

BIX export ignores rows which failed during previous exports.



When a BIX Extraction rule contains the pxObjClass property, the extraction process fails with the below exception.

Error Messages

2017-01-04 10:02:54,236 [fault (self-tuning)'] [ ] [an_app:01.01.01] ( internal.access.ExtractImpl) ERROR an_operaor - Unable to process while reading the source Db AAA-BBB-CCC-Work-DDDD: The page or property AAA_BBB_CCC_WORK_DDDD_W_26.AppClass.AppClassLinks(1).pxObjClass is unmodifiable. Calling method: Details: property is reserved. CurrentValue: XXX-YYY-ZZZ DesiredValue: XXX-YYY-ZZZ-ADCDEFG The page or property a_work_26.a_property(1).pxObjClass is unmodifiable. Calling method: Details: property is reserved. CurrentValue: ABC-Data-DEF DesiredValue: ABC-Data-DEF-EFG

Steps to Reproduce

  1. Run the Extract rule to generate XML and XSD.
  2. After run of extract rule check the logs for failures.
  3. Logs only specified about one case failure but extracted XML will be missing more than one after that case failure. (Log error mages says Index out of bound error)

Root Cause

The reason of the failure is that the pxObjClass associated to the property might have changed in the system. When the system retrieving the records referencing the old pxObjClass, the overriding process to the new pxObjClass will fail as pxObjClass is a read-only property.


The pxObjClass property is not required in the extraction data. Remove the pxObjClass property from the extraction rule makes the extraction successful.

Published January 13, 2017 - Updated January 30, 2017

Have a question? Get answers now.

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