Agent configuration reference

Most of what the ERP Sync agent does is set in Omnilinker, on the connection, and the agent downloads it. The local settings on this page are for the machine the agent runs on. You rarely need to change them.

Where the agent gets its configuration

Source	What it holds
`credentials.dat`	The agent key, Omnilinker’s address, the connection, the ERP database settings and the company number. Written by the tray app’s setup and its Settings…. This is the only place the agent reads the key, the connection and the database settings from.
Omnilinker (cloud)	The connection’s configuration, such as its source warehouse. The agent fetches it every 5 minutes, and sooner when it changes, and keeps a copy in `config-cache.json` for when Omnilinker cannot be reached.
`appsettings.json`, `ErpSync` and `Updates` sections	Local, machine-level settings, described below.
Environment variables	Override `appsettings.json` values.

For the settings in appsettings.json, the order of precedence is, highest first:

Command-line arguments.
Environment variables, named <Section>__<Setting>, for example ErpSync__AutoUpdateEnabled or Updates__Channel.
appsettings.json in the install folder.
The built-in defaults listed below.

Change a setting

Set the value as a machine environment variable, in PowerShell as Administrator, then restart the service. The service reads these settings only when it starts:

[Environment]::SetEnvironmentVariable("ErpSync__AutoUpdateEnabled", "false", "Machine")
Restart-Service OmnilinkerErpSyncService

You can also edit appsettings.json in the install folder, by default C:\Program Files\OmnilinkerErpSync\current, as an administrator, and restart the service.

Every update replaces appsettings.json, and the agent updates itself at night. A change you made in the file is then lost without notice. Environment variables are not affected by updates, so prefer them.

Settings

“Default” is the value the agent uses when the setting is missing from appsettings.json.

Cloud connection

Setting	Type	Default	Meaning
`ApiUrl`	string	`https://omnilinker.pl`	Omnilinker’s address. The address saved by setup in `credentials.dat` takes precedence, so this value is used only before setup has run. Change the address in setup instead (Change next to Server).

Updates

How the agent updates itself. AutoUpdateEnabled is in the ErpSync section. The others are in the Updates section, so their environment variables start with Updates__.

Setting	Type	Default	Meaning
`AutoUpdateEnabled`	boolean	`true`	`false` turns automatic updates off. You then update by hand.
`FeedUrl`	string	none	Where the agent looks for new versions. The shipped file sets `https://releases.omnilinker.com/erpsync`. Empty turns updates off. Do not change it.
`Channel`	string	none	Which releases the agent takes. The shipped file sets `stable`.
`CheckEvery`	time span	`04:00:00`	How often the agent looks for a new version.
`FirstCheckAfter`	time span	`00:05:00`	How long after the service starts it looks for the first time.
`ApplyFrom`	time of day	`01:00`	Start of the nightly window in which a downloaded version is installed, in the computer’s local time.
`ApplyUntil`	time of day	`05:00`	End of that window. The window can run past midnight, for example `22:00` to `04:00`.

A version is installed only inside the window and only while the agent is not running a command from Omnilinker. If installing fails, the agent tries again the next night.

Stock reading

How often the agent reads the stock of a Wapro database. This setting is in the ErpSync:Feeds section, so its environment variable is ErpSync__Feeds__StockDiffIntervalMinutes. Change it only when Omnilinker support or your Wapro partner asks you to, for example for a very busy database.

Setting	Type	Default	Meaning
`StockDiffIntervalMinutes`	whole number	`5`	Minutes between two stock reads, counted from the end of the previous one, while a warehouse of the connection is mapped. A value outside 1 to 60 is brought back into that range. A longer interval makes the ages shown beside the stock grow by as much. See How stock is read.

Reading orders back

How often the agent reads the status, invoices and KSeF numbers of the orders Omnilinker sent to a Wapro database. This setting is in the ErpSync:Feeds section too, so its environment variable is ErpSync__Feeds__SalesOrdersDiffIntervalMinutes. Change it only when Omnilinker support or your Wapro partner asks you to.

Setting	Type	Default	Meaning
`SalesOrdersDiffIntervalMinutes`	whole number	`15`	Minutes between two reads of the orders sent from Omnilinker, counted from the end of the previous one, while the connection has sent an order in the last 90 days. A value outside 5 to 120 is brought back into that range. A longer interval makes a status or an invoice take that much longer to show on the order card. See Invoices.

Reading prices

How often the agent reads the ERP’s prices of a Wapro database, for comparison with yours. This setting is in the ErpSync:Feeds section too, so its environment variable is ErpSync__Feeds__PricesDiffIntervalMinutes. Change it only when Omnilinker support or your Wapro partner asks you to, for example for a very busy database. The agent reads prices only while Omnilinker asks for them; see Prices.

Setting	Type	Default	Meaning
`PricesDiffIntervalMinutes`	whole number	`15`	Minutes between two price reads, counted from the end of the previous one, while Omnilinker asks the agent for prices. A value outside 5 to 120 is brought back into that range. A longer interval makes a difference between the ERP’s prices and yours show up later. See How prices are read.

Lists read by comparison

The agent reads by comparison the lists named in ErpSync:Feeds:DiffStreams. Nothing needs to be set: the default is stock, the orders sent from Omnilinker and prices (Stock, SalesOrders and Prices). If Omnilinker support has set a list of your own, it must include SalesOrders and Prices; without SalesOrders the orders are read only once a day, with the complete read, and the order card says Not read back from ‹ERP› yet for longer, and without Prices the prices are read only once a day, and the comparison is as old as that read. The shipped file is replaced on every update, so keep such a list in appsettings.<Environment>.json or in environment variables. This setting is a list, so an environment variable holds one entry of it and carries the entry’s number. Set one variable for each entry:

[Environment]::SetEnvironmentVariable("ErpSync__Feeds__DiffStreams__0", "Stock", "Machine")
[Environment]::SetEnvironmentVariable("ErpSync__Feeds__DiffStreams__1", "SalesOrders", "Machine")
[Environment]::SetEnvironmentVariable("ErpSync__Feeds__DiffStreams__2", "Prices", "Machine")
Restart-Service OmnilinkerErpSyncService

In appsettings.<Environment>.json the same list is a JSON array: "DiffStreams": [ "Stock", "SalesOrders", "Prices" ]. A single variable without a number, such as ErpSync__Feeds__DiffStreams=Stock,SalesOrders,Prices, does not work: it empties the list, and then neither stock, the orders nor the prices are read by comparison, only once a day with the complete read.

Data root (support only)

Environment variable	Meaning
`OMNILINKER_ERPSYNC_DATA_ROOT`	An absolute path that replaces the data folder, `%ProgramData%\Omnilinker\ErpSync`, for an agent that Omnilinker support runs as a console program (see Install the agent). A value that is not an absolute path is ignored, and the agent’s log says so. Never set it for the installed service.

Logging

The service writes one log file per day to %ProgramData%\Omnilinker\ErpSync\logs (see Local files) and keeps the last 30 files. Each line has a timestamp, the level, the component and the message. Setup, updates and uninstalling add to setup.log in the same folder: done, or one line for each step they could not complete. The log level is fixed: Information for the agent, Warning for framework components. The Logging section in appsettings.json has no effect on the log files.

Local files

The agent keeps two folders on the machine. Install folder: C:\Program Files\OmnilinkerErpSync\current when you install as described in Install the agent. Setup replaces its contents on every update.

File	Contents
`Omnilinker.ErpSync.Service.exe`	The Windows service.
`connectors\wapro\Omnilinker.ErpIntegration.Connectors.Wapro.Host.exe`	The Wapro connector, in a subfolder of its own with its `connector.json`. The service starts it, and it connects to the ERP database as Local System.
`tray\Omnilinker.ErpSync.Tray.exe`	The tray app, in a subfolder of its own.
`appsettings.json`	The settings on this page. Replaced on every update.
`install-service.ps1`, `uninstall-service.ps1`	Only for a portable copy. Setup does not need them.

Data folder: %ProgramData%\Omnilinker\ErpSync, usually C:\ProgramData\Omnilinker\ErpSync. The service and everyone who uses the tray app see the same folder. Setup lets only SYSTEM and administrators change it. Other users can read it, except credentials.dat.

File	Contents
`credentials.dat`	The agent key, Omnilinker’s address, the connection, the ERP database settings and the company number. Encrypted with Windows DPAPI, machine scope: it can be decrypted only on this computer. Only SYSTEM and administrators can open the file.
`agent.db`	The agent’s local SQLite database: its state, and a journal of the commands Omnilinker sent it. `agent.db-wal` and `agent.db-shm` next to it belong to it.
`config-cache.json`	The last configuration the agent received from Omnilinker, used when Omnilinker cannot be reached at start-up.
`logs\erpsync-<yyyyMMdd>.log`	Service log files, one per day, 30 kept. For example `erpsync-20261009.log`.
`logs\setup.log`	What setup, updates and uninstalling could not do.

Uninstalling keeps this folder. See Remove the agent.

Do not delete agent.db while the agent is installed: the agent uses it to finish reporting the commands it was working on.

Earlier versions kept a database called erpsync.db in the Local System profile (C:\Windows\System32\config\systemprofile\AppData\Local\Omnilinker\ErpSync). The agent no longer reads it; you can delete that folder.

Get started

Set up

Map ERP data

Operate

Providers

Reference

Agent configuration reference

Where the agent gets its configuration

Change a setting

Settings

Cloud connection

Updates

Stock reading

Reading orders back

Reading prices

Lists read by comparison

Data root (support only)

Logging

Local files

​Where the agent gets its configuration

​Change a setting

​Settings

​Cloud connection

​Updates

​Stock reading

​Reading orders back

​Reading prices

​Lists read by comparison

​Data root (support only)

​Logging

​Local files

Where the agent gets its configuration

Change a setting

Settings

Cloud connection

Updates

Stock reading

Reading orders back

Reading prices

Lists read by comparison

Data root (support only)

Logging

Local files