Actions

The Actions table contains records that have been created in the Preaction table and converted to actions by running codeunit PreActions-& Actions (99001560) in the Scheduler Job Header.

The Preaction table contains records that the system creates automatically each time the user creates, modifies or deletes a record in a table. The PreAction table does not know how the record should be distributed. In order to find out the distribution, it is necessary to convert the Preaction into an Action. This is the main difference between Preactions and Actions. Preactions know only that the record has been changed. The Actions know that the record has been changed and also how it should be distributed.

The program uses the Location Group Filter in the Actions table to tell where the record (represented by the Action) should be distributed.

The Actions table is used to make Scheduler Subjobs more efficient. When you let the program replicate data between Distribution Location or replicate data to POS Terminal using the by Actions Scheduler Subjob, you can limit the processes to include changed data only by using the Actions table.

Actions must be deleted regularly from the Actions table. If you are not replicating between databases, you need to run the Delete Log (Codeunit 99001486) batch job to delete actions from the Actions table, thereby running no risk of deleting actions which have not been processed by the data exchange procedures.
You can choose to keep a history of actions by filling in the Days Actions Exist field in the Retail Setup table. For.