SA-1287

Summary

The Developer has implemented an exposed class by creating a underlying database table.
The properties of the class contain a combination of simple types (Text, DateTime, etc..) as well as Pages.
However, if one of the Page names is also the beginning part of a name of one of the simple types, when you attempt to save the class an error like the one below will be displayed.

Error Messages

Cannot save instance of class MyClass; it belongs to fully exposed table PRPCDATA.MY_EXT_TABLE in database PegaDATA, but the instance has properties which do not correspond to columns: EmployeeName

In this example the class contains the following properties: -

.EmployeeName (simple Text property)
.Employee (Page)

Steps to Reproduce

1. Create table directly in the database (including a column called EmployeeName)
2. In PRPC: Create a new Concrete data class
3. Create properties in the class akin to the table columns
4. Create a second Data class with the last portion of its class structure called -Employee.
5. Arbitrarily add some properties to this class
6. Return to the class create in step 2
7. Add a new Page property called "Employee" to the class and map it to the class created in step 4.
8. Open the class go to the "External  Mapping" tab.
9. Add an entry to map the "ExployeeName" class to the "EmployeeName" property.
10. Click on Save

Root Cause

This problem has been confirmed as defect in the mechanism to ensure that the external mappings correctly map to columns.

Resolution

This problem is addressed in PRPC 7.1.7