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

Setting up VPD Data Page passing custom properties



When trying to set up Oracle Virtual Private Database (VPD) custom properties following a PDN article, an exception occurred. The link to the article is given below.

Error Messages

[MSG][Exception][STACK][ The property D_VPDInfo.pyCustomPropertyList.pyValue was of mode String while was expecting Page mode. Details: (none) at at

Steps to Reproduce

1. Create a data page for custom properties.
2. Stop the server.
3. Configure a new schema or database in the prconfig.xml file that specifies the database details for the classes identified in Step 2.
4. Start the server.
5. Create a new Data-Admin-DB-Name instance that connects, by using configuration preferences.
6. Open the db-name instance, and click Test Connection.

Root Cause

This is a Pegasystems' product defect.


Perform the following local-change:

1. Prepare data transform.

2. Prepare a data page with List of Embed-NameValuePair.

The referenced PDN article will be updated to reflect the solution here. BUG-246708 is scheduled to be fixed in Pega 7.2.1 to resolve this issue.

Published May 16, 2016 - 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