Subjob View

General setup > Replication > Subjobs > Edit a subjob

What is the view used for?

  • To view and edit a subjob.
  • A subjob specifies the unit of data to replicate. Subjobs can only be run within the context of a job that defines the source and destination locations for the data. Subjobs are, however, independent of jobs in the sense that they can exist on their own without being actually used by a job. In that sense, a subjob can be on the subjob list of zero, one or more jobs.
Fields & buttons Description
Description Edit the description of the subjob.
Replication method

There are three types of replication methods:

  • Normal - The contents of a database table are replicated as a whole. Normal subjobs are suitable for small tables or cases where entire tables must be replicated like when preloading a new store or a POS. Normal subjobs also support replication counters, where a unique index exists that can be used to select records to be replicated. This is useful when replicating transactions from POS, so only the newest records will be replicated.
  • Action - The contents of a database table are replicated by reading a second table, the action table. The action table determines which rows in the main database table have changed and how. Action subjobs are suitable for large tables when you want to minimize data flow by replicating only the changes made in the source location.
  • Stored Procedure - An action table is read on the source location and for each suitable entry in the action table, a stored procedure is run on the destination locations. Stored procedure subjobs are suitable for replicating business logic transactions implemented through stored procedures.
From table design

Enabled only for normal and action subjobs. The table to use as the source for data. This value consists of selecting a particular table design in a particular database design:

To table name Enabled only for normal and action subjobs. The table name to use as the destination of data. Unlike the From table design, this value can be any table name. To aid in specifying a correct name, the same method of selecting a table is used as when selecting the From table design.
Stored procedure name Enabled only for stored procedure subjobs. The name of the stored procedure to run in the destination location.
What to doTbla

Enabled only for normal subjobs.

Specifies how to apply the data at the destination location:

  • Add - All source rows are added at destination. Source records already existing at destination are ignored.
  • Must add - All source rows are added at destination. If a source record exists at destination the operation fails and is rolled back.
  • Delete - All destination rows are deleted. Update, add If source row exists at destination, it is updated, otherwise it is added. Note: This will not work for linked tables.
  • Update, add, delete - All destination rows are deleted and then the source rows are added. Note: This will not work for linked tables.
Enabled Determines if this subjob is enabled. Uncheck this to hide this subjob from the subjob list and prevent it from being added to a job.
Move actions Determines whether actions for this subjob are moved from the source location to the destination location database when job is run. This means that when the subjob is run from the destination location to other locations the actions will be triggered again.
Include flow fields Enabled only for normal and action subjobs. This setting is only relevant when the source table is in a Dynamics NAV database. Checking this field instructs the Scheduler to include NAV flow fields when replicating data.

See also

Last updated: 12th May 2013
Version: LS One 2013.1