Question
Coforge
IN
Last activity: 11 Sep 2020 9:09 EDT
Why is Pega 7.4 data type creating external class/ table in CustomerData schema?
- Add a new/ existing data type using designer studio/ express data explorer
- Configure data type source by selecting key
- Save the data type
- now open the class created and do test connectivity
- it will show as obj-external class
- the table created as part of data type is not having pxObjClass/ pzInskey- This is obvious because it's external
- I have tried to give PegaData as DB while configuring source for Data type but it's showing error " Please select valid DB"
- I have tested this with brand new 7.4 instances and upgraded 7.4 instances. The result is same for both.
Is there any design change happened as part 7.4?
Is there any config missing ?
Accepted Solution
Updated: 11 Sep 2020 9:09 EDT
Coforge
IN
Mesh Link explaining more about this issue but it has limited access.
https://mesh.pega.com/message/334796#334796
Support Article regarding same SA-60573
https://community.pega.com/support/support-articles/unable-create-data-table-post-application-update
Pegasystems Inc.
IN
Hi Pandj,
Hi Pandj,
In Pega 7.4 version, We have a validation ( when rule ) in step 1 of "PegaAccel-Task-. pzCreateLocalDataStorage" activity not to use "PegaDATA" Database for Configuring source for Data types due to some Internal Constraints. It seems PEGA introduced the CustomerData database rule since PEGA 7.4 and when we create the Data Type rule, PEGA is by default adding px related properties. You can use "CustomerData" DB ( which is pointing to PegaDATA ) for Configuring source in Data types for System of Record.
Saltech Consulting
GB
What is the intended purpose of this new database / Schema? It seems to have customer database tables in it. I can see perhaps it may have been intended for some security or logical grouping but how does it then make sense to have the data types created in that?
Rabobank
NL
Is there any update for the reason of this change?
We are not planning to store any customer data but we do need to create some for configuration information. Is there a possible override to this? (Manual script execution for the creation of table in PegaDATA schema?)
Thanks.
Pegasystems Inc.
NL
Also, when creating a product in 7.4 and trying to import in 7.3.1 an error is raised during import process about invalid CustomerData DB. Tried removing the DB-Name instance from package but did not help. Any idea how to work around this?
Accepted Solution
Updated: 11 Sep 2020 9:09 EDT
Coforge
IN
Mesh Link explaining more about this issue but it has limited access.
https://mesh.pega.com/message/334796#334796
Support Article regarding same SA-60573
https://community.pega.com/support/support-articles/unable-create-data-table-post-application-update
Saltech Consulting
GB
I would like to understand why though? Its not ideal just saying 'we have moved something' without the rationale. Customer data is quite a misleading schema name also especially if you are dealing with customer service applications.
Pegasystems Inc.
IN
FYI, Now Pega relaxed the restriction to select only CustomerData when creating local data storage for Datatypes. In 8.1.2, it is fixed and you can create local storage for Datatypes in PegaDATA schema.
Self
IN
You can change the schema to Pegadata from the sources tab.
You can check the document attached .
This post might help you :
https://collaborate.pega.com/question/customer-schema-tables-no-ootb-columns