Question
NTT DATA Italia
IT
Last activity: 16 Sep 2024 8:39 EDT
Upgrade Pega 8.8: warning "Content Dictionary issues"
we are upgrading Pega from version 8.7.0 to 8.8; running the Pre-Update Check the warning type "Content Dictionary issues" appears with the message "The TPMKT-Data-RCAExpiration uses multiple keys in the class definition which is not supported. Update the class with a single key." Key's reconstruction of the class has a very large impact; I would like to know if the warning can be considered as non-blocking or if it is necessary to convert the multiple Key into a single key.
Thanks,
Accepted Solution
Updated: 16 Sep 2024 8:39 EDT
Pegasystems Inc.
IT
@MarijeSchillern and @Gianni Montevidoni
in general you have to avoid multiple keys on the primary and secondary context classes. For the associated data classes is an issue if multiple keys are used in the association.
if it is fine from data model prospective to define the association on a single attribute, you can ignore the warning.
For instance, if you have something like this one:
Primary context: Customer with PK (CustomerID).
- Associated data: RCA-Expiration with PK (CustomerID, CarID)
and the association is just on CustomerID you can avoid the refactoring.
Pegasystems Inc.
GB
@Gianni Montevidoni The issue message indicates that using multiple keys in the class definition is not supported. It is necessary to update the class with a single key to resolve this issue. The warning should not be considered non-blocking, and it is important to convert the multiple keys into a single key to ensure proper functionality
Resolving pre-update issues for Context Dictionary
How to: change/add/remove class keys?
Accepted Solution
Updated: 16 Sep 2024 8:39 EDT
Pegasystems Inc.
IT
@MarijeSchillern and @Gianni Montevidoni
in general you have to avoid multiple keys on the primary and secondary context classes. For the associated data classes is an issue if multiple keys are used in the association.
if it is fine from data model prospective to define the association on a single attribute, you can ignore the warning.
For instance, if you have something like this one:
Primary context: Customer with PK (CustomerID).
- Associated data: RCA-Expiration with PK (CustomerID, CarID)
and the association is just on CustomerID you can avoid the refactoring.