How to get triggers back that show as dropped in a Multi-Site environment

1359 November 1, 2022 477

Summary:

Cause:

Problems with upgrade or customization. Note that you should research and correct other issues that might have arisen first.

Solution:

Here’s how to suggest to proceed.
1) Get everyone out of CP at hub and one remote.
2) Stop replication at hub and remote and backup each site server database.
3) Perform manual pdupgrade at hub and remote using command line syntax below from a directly where you have placed your custom rules file.
Manually update or upgrade the rules file on a replicating first site database (syntax for PDUpgrade on first site):
pdupgrade PDDSN <NameOfRulesFile>.rul /f
Manually update or upgrade the rules file on a replicating remote site database (syntax for PDUpgrade on remote site):
pdupgrade PDDSN <NameOfRulesFile>.rul
4) Ensure pdupgrade is successful at hub and remote. Ensure customization report on both sides no longer show the PDI/U/D triggers as dropped. Enter test transactions such as a ticket,
inventory adjustment, etc and post at each site. Ensure no issues exist with transactions and ensure replication is successful at each site.
5) Once confirmed, optional step 5 to regenerate dxrefeedbackfilter.sql from information on KB920 which I also recommend be done locally at each site with no one in CP.
If no problems are observed, let merchant back into CP. Otherwise restore hub and remote backups and advise.