Change Tracking

In this article

Delete Preaction Table

Preaction Skip Log

Preaction to Action

Change Tracking

Label Utility

Commerce (WI Mgt – PriceOnly)

Commerce Request Mgt

Web Application Sync

Shopify

Delete Logs

LS Central stops logging changes directly to the Preaction table, when using timestamps. The Preaction table is used as a temporary buffer, which is generated at a time as needed from tables being processed using timestamps and relevant records from the Delete Preaction table.

Even though changes can be tracked for individual records in a table by timestamps, it is impossible to track deletion of records that way. Therefore, LSC still needs to log when record is deleted.

Delete Preaction Table

Delete Preaction table keeps track of record deletions. This process still uses Preaction Creation table to control, which table tracks deletions. This table is processed in combination with a timestamp, to create a temporary preaction buffer. A page to show those entries was added and is accessed both directly, and from a Scheduler Job card.

Preaction Skip Log

A new table Preaction Skip Log to keep track of inactive timestamps was added.

• If a record comes into scope when creating the temporary preaction buffer and its current timestamp is also logged as skip, that record does not become part of the preaction buffer.
• A page to show those entries was added and is accessed both directly to and from a Scheduler Job card.

Preaction to Action

Preaction to Action process uses temporary generated preaction buffer. The process uses the Table Distribution Setup to define, which tables create the buffer. This process uses the new Action Creation Timestamp table. A page to show those entries was added and is accessed both directly to, and from the Action List page.

Data Distribution

Data Distribution uses temporary generated preaction buffer when replicating By Action based on preaction.

• This temporary buffer is generated either directly, or through web request, acting against another location.
• The tracking for normal replication and By Action using the Actions table remain as before.
• Associated with this process is the new Preaction Timestamp table that holds the last processed timestamp for each table.
• New pages were added to the Scheduler Job card to list related information in the Actions sections Delete Preactions, Preaction Skip Log and in job section Preaction Timestamps:

Pages that show replication counters were changed to show fields from the Preaction Timestamp table as flow fields.

• This is done to give overview of all process tracking information in one page regardless if it is related to normal jobs or By Action jobs.

In this case the Last Source Counter field shows last preaction entry number used before switching to timestamps.

• New jobs of type by preaction only shows value in Update Last Timestamp field and Deleted Last Entry No. field.

• There is also direct access to the timestamp data through the Preaction Timestamp.

A new action was added to the Scheduler Job card to assist with converting existing tracking data (Replication Counters) into Preaction Timestamps data.

A new web request GetRemotPreactionBuffer, which is an OData V4 based request, was made. This web request is used to get Preaction Timestamps data from another location.

Published and subscribed with all other requests.

Label Utility

Label Utility can use preactions or actions to create needed labels. When creating labels from preaction, it now uses temporary generated preaction buffer, but creating from action is unchanged.

There are two types of process tracking:

• The original (for actions), storing last entry no. on the store card.
• The new one, for preaction in the new Label Creation Timestamp table.

The Label Type is either ITEM or SHELF.  A new page was added to the Store Card to show the Label Creation Timestamp table for labels creation.

Commerce (WI Mgt – PriceOnly)

This process can use preactions or actions to create WI data. When creating WI data from preaction it now uses temporary generated preaction buffer, but creating from action is unchanged.

There are two types of process tracking:

• The original (for actions), storing last entry no. on the store card.

• The new one, for preaction in the new WI Mgt Timestamp table.

A new page was added to the Store Card to show the WI Mgt Timestamp table for WI data creation.

Commerce Request Mgt

The Commerce Request Mgt can be invoked from several users and each request can be called several times to fetch all needed data, therefore it is not practical to generate a new temporary preaction buffer every time it is invoked.

• Commerce Request Mgt uses a new Commerce Action table.
• This table is updated with new scheduler job COMMERS_ACTION (codeunit 10001445).
• Which uses the Preaction Mgt to get preaction buffer for needed tables.
• New field Active For Commerce was added to the Preaction Creation table to control, which table is created Commerce Actions.

 

1. Navigate to the Scheduler Setup card.
2. Click Related.
3. Select Setup.
4. Click Preaction Creation to access the Preaction Creation table.

The system creates Commerce Actions and logs the progress in the Commerce Action Timestamp table.

1. Navigate to the Scheduler Setup card.
2. Click Related.
3. Select Commerce Actions.
4. Click Commerce Action Timestamp to access the Commerce Action Timestamp table.
   

Web Application Sync

The Web Application Sync process uses a temporary generated preaction buffer.

• Instead of storing last timestamps in Timestamptable they are stored in the Web Application Sync Status table for individual registered app.
• The system tracks changes to all its primary tables, and the item distribution table associated with that table.

Shopify

Shopify made a change, and now uses temporary generated preaction buffer. Process tracking is stored under each Shopify job, for regular data distribution jobs, such as codeunits LSCShopifySchContact and LSCShopifySchItem.

Delete Logs

Delete Logs are adjusted to include new log tables.