Limit the first run
When "Artikel Webshop" ran for the first time in March, the entire item master went into the shop in one go: 2,180 jobs. That went well. It could have turned out differently — a wrongly mapped field or a connection that answers differently than expected is just as noticeable with 2,180 records as with fifty, only the cleanup work in the target system is a different matter.
This guide takes the cautious way: first transfer a small selection, look at the result, then open up.
What you can limit here is only the set the route sees at all. The run type is the wrong tool for this: an incremental run picks up from the state of the previous incremental run; the first one has no such state, so it reads the same scope as a full one. And a full run always takes everything the route sees. The tool is therefore the data filter.
There, the filter defines what the route transfers permanently. Here, the same filter is a stopgap that goes away again after the trial run — and the last step of this guide is the one that removes it.
What you need
- Four permissions, each at the Full level: Routes sets the filter, Activation activates the snapshot, Execution starts the run, Automation releases the route at the end. All four are rarely in one person's hands — see Permissions.
- A route that is fully configured and whose source has a fetch endpoint. Only the fetch endpoint gives the route a data scope to limit; without it, the start reports "This route only reacts to events — there is no data scope to run".
Xchange saves every entry automatically. In operation, it takes effect only with the activated configuration snapshot.
1. Keep the automation closed
A new route stays quiet at first, even if it already carries a trigger: on the Execution screen, its switch in the Automation column is off, and the State column shows Never started.
Leave the switch off. You can still start by hand, at any time. Only the route's trigger rests while the switch is off.
If the route has been in operation before, flip the switch before you change the filter. The State column then shows Paused (manual).
2. Set the filter narrower than it is to stay
On the Source data tab, set a data filter that describes a manageable selection — for an item master, e.g. a single item group:
- Expand the Data filter section, Add group, then Add condition.
- Field
ItemsGroupCode, operator equals, value100— the item group Armaturen. - Choose Count matches.
The number next to it is the scope of your trial run. If it is larger than you want, narrow the condition before you continue — afterwards, the transfer has happened. The detailed way with several conditions is described in Narrow down with a data filter.
Choose a selection that you can check in the target system.
3. Activate and start by hand
- Validate and activate the draft — the way is described in Validate and activate.
- Switch to Execution and select the route.
- Choose Start run and confirm the dialog with Start.
"Artikel Webshop" has no change filter; instead of a run type choice, the dialog therefore asks "Start a full run for this route now?". On a route that detects changes, the choice appears there instead — on the first run, both run types lead to the same scope. What the dialog offers when is described in Push manually — a run or a single record.
If the dialog shows a Cleanup checkbox, leave it off. It reports records to the target system that were transferred earlier and have dropped out of the data filter — and your filter is deliberately narrow right now. A cleanup switched on would report to the target system everything you excluded for the trial run. What determines whether the checkbox appears at all is described in Run on a schedule.
4. Look at the result
Wait until the run is through, and look at two things:
- The run itself: how many jobs succeeded and what ended up in Clarification. The way there is described in Check whether a run went through cleanly.
- The target system: look at one of the transferred records there. Are the values in the fields where you expect them? A job can succeed and still have written the wrong value — only the target system shows that.

If something is not right, correct the route and start again — with the same narrow filter. A second trial run costs nothing.
5. Remove the limit
Be sure to carry out this step. If the filter stays in place, the route permanently transfers only the one item group — and the runs report success throughout, so the gap easily goes unnoticed.
- Back to the Source data tab, Data filter section.
- Delete the group: the cross at the far right of its header — its tooltip reads Remove group. Xchange asks: "The group and all its conditions will be removed. This action cannot be undone."
- The section then shows No condition — all records included.
- Validate and activate the draft.
If a filter is to stay permanently, only a wider one than the trial run filter, change the condition and keep the group — and count the matches again.
Finally, release the automation: in Execution, flip the switch in the Automation column. From now on, the route's trigger starts the runs.
What comes next
- Which trigger starts the runs from now on: Choose the right trigger.
- Whether the first run went through cleanly: Check whether a run went through cleanly.
See also
- Restrict with a data filter (guide) — the data filter as a permanent restriction, with several conditions
- Triggering (core concept) — run types, triggers and how they work together