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

Class Key validation failed for class: Rule-Obj-FieldValue,



The developer added a second node, pointing to the same database as an existing working node. Developer portal runs on new node's URL - but certain activities, including re-saving an operator ID, generate errors

Error Messages

Class Key validation failed for class: Rule-Obj-FieldValue, class key value: Embed-Preferences-General-KBCommands/pyKBCommandCategories/UI, reason: Instance not found

Steps to Reproduce

  1. Log on to the developer portal.
  2. Open an operator record.
  3. Attempt to save the operator.

Root Cause

The root cause of this problem is misconfiguration in the operating environment
The prconfig file was configured with settingsource set to file instead of merged


This issue is resolved through the following local change: Updated the prconfig file setting to allow db settings to be used

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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