Posted: 3 Nov 2016 5:17 EDT Last activity: 12 Dec 2016 7:55 EST
Save on Existing Data class throws error
1. We have an existing Data class in this form - "XXX-XXX-Data-Customer" mapped to a Database table and it has certain properties mapped under External Mapping. But when we save this class with no changes to any of the tabs, we get the following error for each property mapped under External Mapping tab.
** Property .XXX specified in the column-property map does not exist.>>
The properties do exist in the application and in an accessible RuleSet version. We did see an answer to this fomr one of the forum questions and that is to re-map the properties by importing the DTD/XST over again. Because the DTD/XSD generation in our case looks to be cumbersome, posting this question.
2. We wanted to verify if the properties are named differently and used with that as the reference in the application, in turn causing this error in some way. But because Edit on classes is disabled in DataModel -> Database class Mapping, we are not able to verify this. Is there an alternative to this?
3. Also, when we do a Test Connection on the Data class, there are these errors thrown. What are the limitations on having more than one concrete class mapped, in case they all have the same parent class?
>> External data table PRPC_DATA_USR.XXX_VW_DECISION_CAR in database PegaDATA has more than one concrete class mapped to it; these classes include XXX-XXX-Data-Customer and XXX-XXX-Data-CustomerAnalytics
>> Class XXX_XXX-Data-Customer is mapped to external data table PRPC_DATA_USR.XXX_VW_DECISION_CAR in database PegaDATA, but the column DT_PORTED_IN_DATE does not have the corresponding Rule-Obj-Property PortedInDate
Do we need an unlocked ruleset version even if we are not adding any new properties to the external mapping tab? Just in the state it is, without any changes to the mapping, the external table mapping is already done. With no changes, on Save, we get these errors.