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).
.pyDataSourceList(1).pyLoadReportDefinition: DataTableEditorReport does not exist or is not a valid entry for this ruleset and its prerequisites
Steps to Reproduce
- Select one external database, schema and table from the Data Base Class Mapping tool
- Choose one of the properties from the columns present on the table and create a property with the same name in the data class
- Change the label of the property to Upper case in the mapping tool
- Click Submit. The tool creates the property which is unavailable and not in upper case
- Create an existing data type for the mapped class
- Go to Records and create a local source
- Click Submit. The error message displays
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:
- Use a different name for the property
- Create an external mapping to explicitly choose the property that supplies it's value to the column
0% found this useful