Question
Omni Fiber
US
Last activity: 6 Jun 2024 9:08 EDT
Primary Key Missing on OOTB tables
Hi, We are seeing primary keys missing on below OOTB tables. We are not able to set database replication without these tables having primary keys. Please suggest on this. We do not have any data on these tables but not allowing set database replication.
pegadata.ced_sample_data
pegadata.conversations_rollingstats
pegadata.crm_data_cti_call
pegadata.crm_data_devicelocation
pegadata.crm_data_propertymap
pegadata.crm_data_routingmap
pegadata.crm_engage_contact_bounceback
pegadata.crm_engage_email_cont_detail
pegadata.crm_engage_email_cont_summary
pegadata.crm_engage_email_org_summary
pegadata.crm_index_accesspermissions
pegadata.crm_index_operemail
pegadata.crm_index_orgdomains
pegadata.crm_sys_queues
pegadata.fw_index_operemail
pegadata.lead_ranking_predictors_data
pegadata.pc_index_distributionchannel
pegadata.pc_link_association_dlmember
pegadata.pegacrm_data_duplicates
pegadata.pr_data_distributionlist
pegadata.pr_emailtemplates
pegadata.pr_log_sycjobs
pegadata.pr_sys_updatescache
pegadata.salesrep_effectiveness_predictors
pegadata.salesrep_effectiveness_snapshot
***Edited by Moderator Marije to add possible Sales Automation/CRM upgrade bug tags***
***Edited by Moderator Marije to support case INC-B6148***
Accepted Solution
Pegasystems Inc.
GB
@Prasanna Kadali I can see that the support ticket was resolved with GCS engineer comment as follows:
------------------------------------------
I have spoken with various product teams and the tables the PKs are being requested for have never had PKs defined on them. The below chart contains the suggestions for the PKs for these tables. This is a one off list that is being provided to you in order to allow your db replication to work. This is not something that would be a product change.
Provided list:
@Prasanna Kadali I can see that the support ticket was resolved with GCS engineer comment as follows:
------------------------------------------
I have spoken with various product teams and the tables the PKs are being requested for have never had PKs defined on them. The below chart contains the suggestions for the PKs for these tables. This is a one off list that is being provided to you in order to allow your db replication to work. This is not something that would be a product change.
Provided list:
| TABLE | NOTES | ACTIONS |
| pegadata.ced_sample_data | sample data | PK on ID |
| pegadata.conversations_rollingstats | pegachat | PK on czQueueName |
| pegadata.crm_data_cti_call | pegacall | PK on pzInskey |
| pegadata.crm_data_devicelocation | used for mobile for late for meetings notifications | PK on DeviceIdentifier |
| pegadata.crm_data_propertymap | old bulk data loaders / not being used | DROP table - sample data |
| pegadata.crm_data_routingmap | lead routing / not being used | DROP table - sample data |
| pegadata.crm_engage_contact_bounceback | sample data | DROP table - sample data |
| pegadata.crm_engage_email_cont_detail | sample data | PK on ID |
| pegadata.crm_engage_email_cont_summary | sample data | PK on ID |
| pegadata.crm_engage_email_org_summary | sample data | Drop Table - sample data |
| pegadata.crm_index_accesspermissions | index classes | PK on pzInsKey |
| pegadata.crm_index_operemail | index classes | PK on pzInsKey |
| pegadata.crm_index_orgdomains | index classes | PK on pzInsKey |
| pegadata.crm_sys_queues | Agents | PK on pyItemID |
| pegadata.fw_index_operemail | operator access index table | PK on pzInsKey |
| pegadata.lead_ranking_predictors_data | lead ranking | PK on SnapshotDate and LeadID |
| pegadata.pc_index_distributionchannel | distibution list index tables | PK on pzInsKey |
| pegadata.pc_link_association_dlmember | distribution list member | PK on pxLindedRefFrom and pxLinkedRefTo |
| pegadata.pegacrm_data_duplicates | duplicates maintenance (lead dedup) | PK on ObjectKey and DuplicateObjectKey |
| pegadata.pr_data_distributionlist | distribution list | PK on pyID |
| pegadata.pr_emailtemplates | email templates | PK on CorrInsKey |
| pegadata.pr_log_sycjobs | exchange sync logger entries | PK on pyCreateDateTime |
| pegadata.pr_sys_updatescache | platform | PK on pzKeyString |
| pegadata.salesrep_effectiveness_predictors | sales coach predictors | PK on SnapShotDate and pyID |
| pegadata.salesrep_effectiveness_snapshot | sales coach snapshot | PK on pyUserIdentifier and SnapshotDay |
----------------
Pegasystems Inc.
GB
@Prasanna Kadali please log a support incident via the MSP and provide the INC ticket number here so that we can help track it.
Updated: 13 Feb 2024 11:04 EST
Omni Fiber
US
@MarijeSchillern This is the incident ticket INC-B6148
Accepted Solution
Pegasystems Inc.
GB
@Prasanna Kadali I can see that the support ticket was resolved with GCS engineer comment as follows:
------------------------------------------
I have spoken with various product teams and the tables the PKs are being requested for have never had PKs defined on them. The below chart contains the suggestions for the PKs for these tables. This is a one off list that is being provided to you in order to allow your db replication to work. This is not something that would be a product change.
Provided list:
@Prasanna Kadali I can see that the support ticket was resolved with GCS engineer comment as follows:
------------------------------------------
I have spoken with various product teams and the tables the PKs are being requested for have never had PKs defined on them. The below chart contains the suggestions for the PKs for these tables. This is a one off list that is being provided to you in order to allow your db replication to work. This is not something that would be a product change.
Provided list:
| TABLE | NOTES | ACTIONS |
| pegadata.ced_sample_data | sample data | PK on ID |
| pegadata.conversations_rollingstats | pegachat | PK on czQueueName |
| pegadata.crm_data_cti_call | pegacall | PK on pzInskey |
| pegadata.crm_data_devicelocation | used for mobile for late for meetings notifications | PK on DeviceIdentifier |
| pegadata.crm_data_propertymap | old bulk data loaders / not being used | DROP table - sample data |
| pegadata.crm_data_routingmap | lead routing / not being used | DROP table - sample data |
| pegadata.crm_engage_contact_bounceback | sample data | DROP table - sample data |
| pegadata.crm_engage_email_cont_detail | sample data | PK on ID |
| pegadata.crm_engage_email_cont_summary | sample data | PK on ID |
| pegadata.crm_engage_email_org_summary | sample data | Drop Table - sample data |
| pegadata.crm_index_accesspermissions | index classes | PK on pzInsKey |
| pegadata.crm_index_operemail | index classes | PK on pzInsKey |
| pegadata.crm_index_orgdomains | index classes | PK on pzInsKey |
| pegadata.crm_sys_queues | Agents | PK on pyItemID |
| pegadata.fw_index_operemail | operator access index table | PK on pzInsKey |
| pegadata.lead_ranking_predictors_data | lead ranking | PK on SnapshotDate and LeadID |
| pegadata.pc_index_distributionchannel | distibution list index tables | PK on pzInsKey |
| pegadata.pc_link_association_dlmember | distribution list member | PK on pxLindedRefFrom and pxLinkedRefTo |
| pegadata.pegacrm_data_duplicates | duplicates maintenance (lead dedup) | PK on ObjectKey and DuplicateObjectKey |
| pegadata.pr_data_distributionlist | distribution list | PK on pyID |
| pegadata.pr_emailtemplates | email templates | PK on CorrInsKey |
| pegadata.pr_log_sycjobs | exchange sync logger entries | PK on pyCreateDateTime |
| pegadata.pr_sys_updatescache | platform | PK on pzKeyString |
| pegadata.salesrep_effectiveness_predictors | sales coach predictors | PK on SnapShotDate and pyID |
| pegadata.salesrep_effectiveness_snapshot | sales coach snapshot | PK on pyUserIdentifier and SnapshotDay |
----------------