Skip to main content
A field mapping connects one field in your ERP to one field in Omnilinker, for example the Wapro column INDEKS_KATALOGOWY to the product’s SKU. When a product or brand arrives from the ERP, Omnilinker reads the ERP fields named in your mappings, applies any default value and transform, and writes the result to the catalog. Mappings belong to a connection and an entity type. You edit them on the connection’s Field Mappings tab.
Only Product and Brand mappings change how data is imported. For price levels, product prices, warehouses and stock the provider uses a fixed set of fields. Their default mappings are listed below so you can see which ERP columns are read, but editing them has no effect.

​
Open the field mappings

  1. Open ERP Integration > Connections, and choose Details on the connection.
  2. Open the Field Mappings tab.
  3. Choose the entity type in the Entity Type list at the top of the tab.
The table shows one row per mapping: ERP Field, Catalog Field, Required, Default Value, Transform, Sync Direction and Hash. To change mappings you need the Manage Field Mappings permission.

​
Apply the provider’s default mappings

Start from the provider’s defaults rather than typing every mapping.
1

Choose the entity type

Pick Product in the Entity Type list.
2

Load the defaults

Click Load Provider Defaults. A window lists the provider’s mappings for that entity type, with a Status column: New for mappings you do not have yet, Will Update for ERP fields you already map.
3

Choose which to apply

New mappings are selected for you. Existing ones are not, so your changes are kept unless you select them. Use Select All or Deselect All if needed. Open Mapping Descriptions to read what each ERP field holds.
4

Apply them

Click Apply Selected. The mappings are added to the table, marked New or Modified. They are not saved yet.
5

Save

Click Save All.
Repeat for Brand. Mappings added this way get From ERP Only as their Sync Direction and are included in the hash check. If Omnilinker says No default mappings available for this provider and entity type., add the mappings yourself from Wapro default mappings.

​
Add or edit a mapping

1

Open the mapping window

Click Add Mapping, or the edit icon on a row.
2

Pick the fields

In ERP Field, pick a field or type its name. In Catalog Field, pick the Omnilinker field or type its name. Fields that Omnilinker requires carry a Required badge.
3

Set the options

Fill in the options described in Mapping options.
4

Add it to the table

Click Add (or Save when editing).
5

Save

Click Save All at the bottom of the tab.
Changes you make on this tab are held until you save them. While you have unsaved changes, the tab shows Unsaved Changes. Save All stores them. Discard Changes reverts them. The delete icon on a row removes the mapping, also only once you click Save All. Saved mappings take effect within about a minute.

​
Mapping options

Sync Direction does not filter anything yet. Every product and brand mapping is applied to data coming from the ERP, even one set to No Sync or To ERP Only. To stop an ERP field from reaching Omnilinker, delete its mapping.

​
Required fields

Every product needs an SKU and a name. Map an ERP field to Sku and to Name. Without them, product changes fail. Brands need Name.

​
Transforms

A transform changes the value of an ERP field before Omnilinker stores it. Chain several with semicolons. They run left to right, so TRIM;UPPERCASE;PREFIX:SKU- first trims spaces, then upper-cases, then adds the prefix. The Transform Reference section of the mapping window lists them too. Things to know:
  • Transform names are not case-sensitive. Prefix and suffix text keeps its case.
  • Numbers in ROUND, MULTIPLY and DIVIDE use a dot as the decimal separator, for example MULTIPLY:0.01.
  • REPLACE splits on colons, so it cannot replace a colon.
  • An unknown transform, or one that does not fit the value (such as ROUND on text), leaves the value unchanged.
  • The Default Value is applied before the transforms, so transforms also apply to it.
  • An empty ERP field with no Default Value skips the transforms entirely. To fill empty fields, use Default Value rather than DEFAULT:.

​
Change detection

In hash scan mode the agent decides whether a product or brand changed by comparing a fingerprint (hash) of its fields with the last one it sent. Only fields with Include in hash check ticked go into the fingerprint. A change to an unticked field alone is not sent until another, hashed field changes. The Hash column shows a filled dot and the priority for hashed fields, and an empty dot for the others. Adding a field to the hash, or removing one, changes every fingerprint. The next hash scan then sends all products again. This is safe, but on a large catalog it takes a while. In WFM_INT change tracking mode the hash settings only affect the weekly reconciliation pass.

​
Wapro default mappings

These are the Wapro provider’s default mappings. “Applied” says whether editing the mapping changes the import.

​
Product

Applied: yes. If a product’s brand has not reached Omnilinker yet, the product is saved without a brand. The link is added the next time the product syncs after the brand arrives.

​
Brand

Applied: yes. Wapro has no separate brand list. The agent builds brands from the distinct PRODUCENT values on articles, ignoring differences in upper and lower case.

​
Price level

Applied: no (fixed).

​
Product price

Applied: no (fixed).

​
Warehouse

Applied: no (fixed).

​
Stock

Applied: no (fixed). Available stock is calculated as on hand minus quantity on open documents minus reserved.

​
Troubleshooting

A mapping marked Required Field had no value and no default. Check that the ERP field has data, add a Default Value, or clear Required Field. The message on the Sync Logs tab names the field.
The ERP overwrites every mapped field each time the product changes there. Change the value in the ERP instead, or delete the mapping so the ERP stops supplying that field.
In hash scan mode, check that the field is included in the hash check. See Change detection.
See also Troubleshooting.