We are seeing this issue with JSON request and response properties not getting mapped with existing properties created in @baseClass in our application. We have a property BusinessLine created in Data- class and USCitizen created in @baseClass in an existing application long back. Now we are trying to consume a REST service which has both these properties in it's response JSON as businessLine and usCitizen. As, the case is not matching Pega is not copying the values. We tried to create these properties with matching case in REST Data class but Pega is not allowing us throwing the below error,
This record has 2 Errors in 2 places
A case mismatch has been found for this property: 'businessLine' doesn't match 'BusinessLine'
Definition required to confirm to Data-.BusinessLine instance created 20181213T073945.991 GMT.
Pega created the properties using qulaifiers with pzExternalName but still it's not working. This is stopping us without progressing further. Any help would be appreciated.
The goal is to have Property rules available to the Response Class whose pzExternalName qualifiers are set to 'businessLine' and 'usCitizen'.
If you can't specialize the existing BusinessLine and USCitizen properties to do this, then perhaps create new properties in your Integration data model with different names (e.g. BusinessLineFromJSON, USCitizenFromJSON) with the pzExternalName qualifiers matching the names from your JSON. These properties are not typically visible to your case or business data model so its less of an issue that these aren't named informatively. Then have your Response Data Transform map the new properties from your *-Int-*Response class to wherever you need them in your *-Data-* or *-Work-* class that is using the data.