Discussion
Morgan Stanley
IN
Last activity: 13 Jun 2022 9:27 EDT
Errors in test connectivity that table contains px, py, or pz property
Hi
i have created a data type with come columns like pxCreateDateTime, pxCreateOperator, pyGUID as key..
When i click on test connectivity its throwing the below errors:
Class TGB-HRApps-Data-TestPX is mapped to table pegadata.pr_tgb_hrapps_data_testpx in CustomerData.
This is an Obj-external class. You may access the class with Obj- activity methods.
Issues:
 |
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxCreateDateTime |
|
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxCreateOperator |
|
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxCreateOpName |
|
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxCreateSystemID |
|
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxUpdateDateTime |
|
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxUpdateOperator |
|
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxUpdateOpName |
|
Class TGB-HRApps-Data-TestPX is mapped to foreign data table pegadata.pr_tgb_hrapps_data_testpx in database CustomerData, but it contains a px, py, or pz property: pxUpdateSystemID |
Should i ignore them?
I'm on 7.4 version.
***Edited by Moderator: Pallavi to update platform capability tags***
Updated: 27 Apr 2022 16:38 EDT
Pegasystems Inc.
IN
Hi Haria,
Please find below explanation :
In Pega7.4, configure source behavior is modified
All user defined tables (created via configured source) will be created only in CustomerDATA schema. PegaDATA will be used only for Pega shipped tables.
If CustomerDATA uses same connection as PegaDATA , tables will be created in PegaDATA configured physical DB /schema.
If CustomerDATA is configured with some other physical DB/Schema , then tables will be created into that physical DB/Schema.
But to customer and DADT ,it will be always created in CustomerData .
Coming to warnings , these are just warnings. These warnings will not create any issue .
While Configuring sources by default pxCreate* and pxUpdate* properties (total 8 properties) get listed for optimization.
Users can delete these options if they do not want to expose these columns.
For reference:
https://community.pega.com/support/support-articles/unable-create-data-table-post-application-update
Bank of America
US
I observed one issue here. My user defined tables have the same warning as posted above in this thread and the explaination given here make sense for the change now.
But I am facing the issue as my pxCommitDateTime is not getting updated when instances are getting saved for my user defined class. What could be the reasoning?
We need pxCommitDateTime to get update on my these class instances in order for Bix Extract rule to use for incremental data extract.
Appreciate your response on this.
Updated: 27 Apr 2022 16:38 EDT
Morgan Stanley
IN
This is a good candidate for a feedback. Can anyone please raise a feedback item to the platform team about the same. The warnings are misleading. There’s nothing wrong in having columns with names starting with px, py and pz as they are just names.
Pegasystems Inc.
GB
@Avinash.Haridasu FDBK-30011 already exists.