Question

13
Replies
320
Views
Bob Reawaruw (BobReawaruw)
Atos
PEGA Senior Architect
Atos
NL
BobReawaruw Member since 2018 58 posts
Atos
Posted: October 28, 2019
Last activity: October 30, 2019
Posted: 28 Oct 2019 1:33 EDT
Last activity: 30 Oct 2019 3:28 EDT
Closed

Class key property returning issue

Issue:

  • Using the “create datatype” functionality, I have created the class: “Data-XXX”.
  • Data-XXX contains properties .X, .Y and .Z.
  • Where .Y was set as key.
  • The requirements changed and .Y could have the same value twice.
  • Thus, on the “Data-XXX”-rule settings I selected the automatic generation of the key, using .pyGUID.

However, PEGA 8.1.5 still requires .Y to be unique.

  • So, I have deleted all datapages, report def, properties and the class-rule of Data-XXX.
  • Now, I have created the datatype again, with the same name “Data-XXX” and properties.
  • The issue returns, .Y is required and has to be unique.

After checking the DB schema, using the “modify schema” functionality, it appears .Y column could be the issue.

Which tools are best to be used in adjusting the column properties in the DB schema?

Pega Platform Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.