When working with the app, several task areas arise.
Tasks After the Upgrade
1. In the previous version of the replication, "manual replication" was permanently set for the following tables:
Table 15 - G/L Account
Table 18 - Customer
Table 23 - Vendor
Table 27 - Item
Table 152 - Resource Group
Table 167 - Project
Table 5050 - Contact
"Manual replication" can now be configured individually for most tables. Further details can be found in the corresponding chapters. You must carry this out or verify it.
If you previously used the value "Operative Only" in the parameter "Transfer to Company" within "RPL Transfer to Companies Default Values", this value was automatically changed to "Company Group" during the upgrade.
You must now create this company group manually!!!
You may, for example, name it "Operative Only" and assign the companies that were marked as operative in the legacy system to this group.
The categorization “Operative Only” is no longer supported directly by the companies.
(Note: Therefore, the company group described above is required.)
If you used the option "Only Certain Companies" for tables or fields in the legacy system, you must review and, if necessary, correct these settings in the new system, as in many cases they cannot be transferred automatically by the upgrade routine.
In general, all other table settings must also be reviewed, as during an upgrade table names, field names, or field numbers of replicated tables may change. The upgrade routine cannot automatically account for such changes.
2. Permission sets for users must be reassigned after the upgrade:
RPLNormalNX → NVXRPL
RPLSuperNX → NVXRPL, Setup
Interface Between Databases
When testing the interface connection between two databases, you must assume that HTTP requests are automatically blocked in a test database.
In the extension settings entry, the checkbox "Allow HttpClient Requests" must be activated for a test database so that the connection can function.
More information can be found in the Microsoft documentation:
HttpClient data type - Business Central | Microsoft Learn
Job Queues
The action "Run Replication" starts the processing of all replication entries that have not yet been processed. This action can also be executed via the job queue.
Codeunit 70161755 - "NVXRPL Start Replication"