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

Database-Config-KeyPropertyNotExposed error in log



On indexing work items, the Database-Config-KeyPropertyNotExposed error is generated in the log.

Error Messages

Caused by: Database-Config-KeyPropertyNotExposed PegaIns-Interface-Contact-CommunicationOptions PrimaryCommunication at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?] at ~[prprivate-data.jar:?]

Steps to Reproduce

Verify the mapped keys for the PegaApp-Interface-Contact-CommunicationOptions class and the composite primary keys of the pa_communication_options table.

Root Cause

A defect in Pegasystems’ code or rules.
The keys were mapped incorrectly.


Apply HFix-63728.
Suggest Edit

Published December 2, 2021

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