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

Issue with adding an existing datatype



User maps the external database table to a class and creates properties according to columns on the table using the Database Table Class Mapping tool. If the property which must be created while mapping is already present in the inheritance, the property is created as unavailable and is not case sensitive. When the user creates a data type local source for the class which is created, an error occurs as the property validation fails during the validateReportDesignTab activity in 3.12 step (obj-validate for the property).

Error Messages

.pyDataSourceList(1).pyLoadReportDefinition: DataTableEditorReport does not exist or is not a valid entry for this ruleset and its prerequisites

Steps to Reproduce

  1. Select one external database, schema and table from the Data Base Class Mapping tool 
  2. Choose one of the properties from the columns present on the table and create a property with the same name in the data class
  3. Change the label of the property to Upper case in the mapping tool
  4. Click Submit. The tool creates the property which is unavailable and not in upper case 
  5. Create an existing data type for the mapped class
  6. Go to Records and create a local source 
  7. Click Submit. The error message displays 

Root Cause

A defect in Pegasystems’ code or rules. While mapping a property with an external table and the given column name which is the same as any existing property in the hierarchy but with all upper case letters, a property with uppercase is created and marked as unavailable. While adding the data type to the Datatype Explorer and a local data source, an error occurs since the property is unavailable.


The issue is scheduled to be addressed in a future Pega release. 

Perform the following local-change: 
  1. Use a different name for the property
  2. Create an external mapping to explicitly choose the property that supplies it's value to the column


Published December 2, 2021

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