Creating, deleting, or modifying a record in a table set up for replication (see "Replication Setup Tables") triggers the creation of a data transfer for each configured company. These data transfers can be managed using the "RPL Replication" page. When a new record is created, an "Insert" data transfer is generated to create the primary key in the respective target company. The remaining fields are then populated using the "Modify" data transfer. Deleting a table record generates a "Delete" data transfer. Each data transfer contains detailed rows with information about the individual fields.
Using the "Execute Replication" action initiates the processing of pending data transfers. This action can also be performed through a job queue.
All processed entries are marked as "Assumed" along with the date and time of acceptance.
If an error occurs during processing, the "Error" flag is set, and the date and time of the error are recorded. If an error occurs, the processing of all subsequent replication sets from the affected company is stopped. However, replication continues for all other companies. Once the error is resolved, replication for the affected company resumes at this point.
The "Skip" flag allows skipping the processing of a data transfer to proceed with the processing of subsequent records. Removing the "Skip" flag will trigger another attempt to accept the skipped data transfer during replication.
Within a company, the processing in replication is always based on the ascending order of the sequence number. However, for clarity, the data is displayed in descending order.
Replication can also be performed within individual companies, considering only the data transfers for the respective company.
Replication of Main Master Data
For "Main Master Data," replication of records does not occur automatically but needs to be enabled for each individual record. Once you have completed creating the record in the master data company, run the "Execute Replication" function. Additionally, you can choose which companies the record should be replicated to.
Execute replication with filter
This function is only displayed if you have received the corresponding authorization in the "User setup".
When the function is executed, the "Execute replication" function is carried out as usual. However, only those data transfer records that have been filtered in the currently displayed window are processed.
Replication between Databases
During cross-database replication, data transfers from the base database are acquired using the "Transfer from Base-Database" action.
If an error occurs during this process, the transfer is interrupted, and the corresponding data transfer is marked accordingly.
To process records for the clients of this database, the "Execute Replication" action must be selected here as well.
The master data company in the remote database is not strictly required. However, if you want to initiate data transfers for all companies with ONE execution of the "Execute Replication" function, you will need a master data cmpany in the remote database as well.
When fetching replication setup tables, all definitions are always transferred. This occurs automatically during the transfer of data transfers. In a remote database, these definitions should not be altered anymore.
The actions "Transfer from Base Database" and "Execute Replication" can be automated using a task queue (Report 61882 - RPLTransferRemoteDTNVX and Codeunit 61883 - RPLStartReplicationNVX).
