Sync configuration

A connection syncs only the kinds of data you give it a sync configuration for. You create one sync configuration per entity type (products, brands, prices and so on) on the connection’s Sync Configuration tab. Settings that apply to the whole connection, such as the change tracking mode, live in the connection’s Edit Connection window.

​

Add a sync configuration

You need the Manage Sync Configuration permission. Delete behavior and the timing settings are not in the Add Configuration window. To change them, edit the configuration after you create it. For Wapro, add a configuration for each of these entity types: Product, Brand, Price Level, Product Price, Warehouse and Stock. The agent only sends products and brands when their configuration exists and is enabled. Product prices and warehouses are sent unless you add their configuration and disable it.

​

Edit, disable or delete a configuration

On the Sync Configuration tab, each row shows Entity Type, Direction, Master Source and whether it is Enabled or Disabled.

• Click the edit icon to open Edit Sync Configuration.
• Click Disable to stop syncing that entity type, and Enable to resume.
• Click Delete to remove the configuration.

Changes reach the agent within a few minutes. The agent picks up new configuration on its next heartbeat, which runs every minute, and checks for new configuration every 5 minutes in any case.

​

Settings

​

Basic settings

A new configuration defaults to Bidirectional and ERP. The Wapro defaults are From ERP and ERP.

​

Sync triggers

On Create, On Update and On Delete (shown as Sync on Create, Sync on Update and Sync on Delete when you add a configuration) say which kinds of change to sync. They are intended for syncing from Omnilinker to the ERP. Changes from the ERP are applied whatever you tick here.

​

Delete behavior

Delete behavior only concerns deletes going from Omnilinker to the ERP: Omnilinker does not write to your ERP yet, so none of these options changes your ERP today. Leave it on Skip.

​

Advanced timing settings

Expand Advanced Timing Settings in Edit Sync Configuration to see these. When collapsed, a one-line summary shows the current values.

​

What the settings do today

Not every setting on this screen changes what the agent does in the current version. This table shows which ones the agent uses.

​

Connection-wide sync settings

These settings apply to every entity type on the connection. Open ERP Integration > Connections, choose Edit on the connection, and find them under Sync Settings. You need the Edit ERP Connection permission.

​

Change tracking mode

In both modes the agent also uploads price levels, warehouses and other reference data every day, and bundle compositions every 6 hours. Switching to WFM_INT change tracking takes two steps, in this order: The agent uses WFM_INT only when both are true. If the connection asks for WFM_INT but the agent is not registered, the agent keeps using hash scan. The Agent tab on the connection shows the mode the agent is actually using. To go back, set Change tracking mode to Hash scan. To also remove the registration from the ERP database, click Disable Change Tracking in the tray app.

​

Bundle pricing

Bundle (Zestaw) price source decides how the price of a bundle product imported from the ERP is stored: This setting affects bundle products only. Simple products are unchanged.

​

How changes flow

From the ERP to Omnilinker, every change takes the same path:

1. The agent detects the change in the ERP database, using hash scan or WFM_INT.
2. The agent saves it in its local outbox before it marks the change as read in the ERP. If the internet connection drops, changes wait in the outbox.
3. Every 5 seconds the agent sends pending changes to Omnilinker over HTTPS, in compressed batches.
4. Omnilinker applies your field mappings to products and brands, then creates or updates the catalog product, brand, price level or price. Warehouse and stock changes go to Inventory.
5. Each change is recorded on the connection’s Sync Logs tab. See Monitoring.

Omnilinker skips a change, rather than failing it, when something it depends on is not there yet. For example, a price whose price level is not mapped, or stock for a product that has not arrived yet. These changes are applied later, once the dependency exists. See Reference items. When changes arrive out of order, Omnilinker keeps the newest. An update carrying an older ERP timestamp than the one already applied is skipped.

​

From Omnilinker to the ERP

Writing to the ERP is not available yet. Editing a product in Omnilinker does not change it in the ERP. The next change to that product in the ERP overwrites the fields that come from the ERP.

​

How often data syncs

These are the agent’s defaults. The agent’s own intervals are set on the agent computer. See Configuration reference.

​

Initial sync

There is no separate full-sync setting. The first sync happens on its own:

• Hash scan: on the first scan the agent has no fingerprints yet, so it sends every product and brand.
• WFM_INT change tracking: registration marks every existing record as new, so the agent sends everything. It sends reference data and warehouses first, then products and stock, then prices, so that each item’s dependencies arrive before it.

A first sync of a large catalog can take hours. Adding a field to the fingerprint (see Include in hash check) also makes the next hash scan send every product again.

​

Recommended values for Wapro

These are the Wapro provider’s defaults, which Load Provider Defaults fills in. All use Skip for Delete Behavior. Product prices, warehouses and stock need WFM_INT change tracking.

​

Next steps