Skip to main content

Release notes

This page documents all functionally relevant changes and new features per version of Xchange. It lists what you notice on screen.

The version number denotes the Xchange product release. Each section additionally lists the contained service and UI versions, exactly as shown in the application's Overview.

1.1 Current · 2026-10-28​

Included components: Service v1.1.0 · UI v1.1.0

At a glance: Steps address target records through the Item endpoint, send batch calls and find list rows again when updating. Conflict rules decide per field which value applies, and own changes reported back are recognized. Internal routes transfer within SAP Business One, additional data reads a further object, and running runs show their pace.

Before you update​

  • ⚠️ Update the services first, then the UI — otherwise it reports "Service and UI Do Not Match".
  • ⚠️ The database update requires a Service Layer restart — the database state moves from 23 to 37.
  • ⚠️ Check routes that convert 01/02/2026 — with Day first this is now 1 February, previously 2 January.
  • ⚠️ Activate the configuration again if additional data checks "is empty" or "is not empty" — until then this additional data cannot be determined.
  • ⚠️ Check mappings with Current timestamp if the server does not run in UTC — the value now uses the system's time zone, previously UTC.

New​

Configuration​

  • A step addresses the target record through the Item endpoint — one row per key placeholder, whose Value comes from the mapping or the source.
  • List rows are found again through Link By — a line with a swapped item is updated instead of appended, Search By controls the target-system search.
  • Lists write simple values — through the Result type Value list.
  • A writing step sends several records in one Batch call — each record keeps its own outcome.
  • A step can run once per element of a list — through Execution Per element, with List and Element key.
  • Additional data reads a further object beside the main object — linked by one or more rows, optionally with its sub-object.
  • Behavior tab with Deletion marker — conditions mark a source record as deleted.
  • Create with Target system lookup checks the target system first — a match ends as "Already present".
  • Conflict rules decide per field which value applies — in the Conflicts section of the Behavior tab, for whole lists too.
  • Internal routes transfer data within SAP Business One — through the Direction Internal, with an event trigger too.
  • Read changes only also detects changes by date — through Source filters by date, for sources without a change token.
  • A queue delivers several messages per fetch — through Fetch returns, existing routes stay on one message.
  • The Acknowledgment endpoint takes the Message ID as a placeholder and suggests endpoints — Acknowledgment rows also take constant values.
  • First available value takes the first alternative that yields a value — each alternative and each case has its own transformation.
  • Next reference date transformation — inserts the next fixed reference date from a date, e.g. 30 June.
  • Dispatch rules and Conditional value mapping cases hold up to three groups — it is enough for one to match.
  • A list's Filter offers "contains value" — for fields that are lists themselves.
  • A mapping optionally writes only on create or only on update — through Write in the Row settings.
  • Lists also change rows the message does not deliver — on the Existing rows tab, Fill with new rows fills Empty rows.
  • Renamed additional data carries every path to the old name along — with the number of adjusted references.
  • Display field under Record identification — sets which value names a record in the history.
  • Load from source also finds reference data by display value — previously Load by key.

Operation​

  • The operation detail shows the Attempt history and each step's Action — for deletions the Reason, for the sent message the batch call.
  • New clarification reasons for writing by key — among others "Key contradicts object link".
  • A dedicated message when service and UI do not match — with both versions, it reloads once they match.
  • Test versions are marked — with a production license by a notice on every screen, in System Status as "Test version".
  • The service log counts outgoing calls per target and caller every five minutes — with methods, response times and errors.
  • Own changes reported back by a system are recognized — per list row too, they end as "Skipped (echo detected)".
  • Field conflicts are decided per field in Clarification — with Source or Target system as Value to apply, per row in lists.
  • Linked list rows are checked against their key — one point per contradiction in Clarification, Accept decisions applies them all.
  • For "Several target records", choose the intended one through Set object link — Clarification shows the records found.
  • Running runs show their pace and expected end in Execution — if a run stalls, its row says so.
  • The History filters by Step status and counts the matches — across all operations, not just the loaded rows.
  • The history shows a run's read position — through the info icon at Run, at start and at end.
  • For a Per element step, the history shows each element in its own row — elements that cannot be told apart stop the operation with "Elements cannot be told apart".
  • History and Clarification show a record's readable value — e.g. the document number, in the search too.
  • Transfer individually also accepts the display value — by key now for REST sources with a Single-fetch endpoint too.
  • Parallel processing under Settings — Max. concurrent operations limits the operations of all routes, default 8.
  • A route or connection with unreadable content is locked — instead of running on with an empty filter.

Changed​

Configuration​

  • The Delete behavior sits on the Behavior tab — and applies to every processing route.
  • Routes no longer have an Object type — the route list's Object column shows what the route processes, the create dialog no longer asks for it.
  • Each additional-data link is a row with two fields — over any searchable field, custom fields included; long-text fields are no longer offered.
  • Search field in the target system only offers searchable fields — an already chosen other one blocks activation.
  • A target endpoint without create reports "The target endpoint does not allow creating records" — for Create and Create or update.
  • Stricter validation before activation — among others for additional data without Fields and paths to additional data not configured.
  • Object pickers show the Service Layer name, the description in grey beside it — for Fetch endpoint, Target endpoint, Other object and in additional data.
  • Required asterisks follow the current setting — on every route tab, in connections and dialogs, e.g. after changing the Authentication type.
  • Entries of an object deleted since the validation count as "Resolved" in the checklist — Next and Previous skip them.
  • Additional data on the main record has its own Link to main record — an existing condition stands as a link after the update.
  • "does not equal" in additional-data conditions keeps records with an empty field — as in the route filter.
  • With REST targets, Target field offers the fields of the Write intent — Validate measures target fields against the same form.
  • A step's response holds the record from the target system after writing — even if the target system returns none.
  • Date functions read a date with slashes per the connection's setting — as the conditions do.
  • Single-fetch endpoint and Key field follow the source catalog on save — if a value differs, Reset to derived value applies the expected one.
  • REST-source routes report SourceSystem "REST" in the message header — previously "SAP_B1".
  • Conditional value mapping cases and concatenation parts move by the handle — no longer by buttons.
  • Changes to a Dispatch rule are saved immediately — Done only closes the rule.
  • "Last connection test failed" is a warning — and no longer prevents Activate.
  • Open configuration versions with converted data filters are "Not Validated" after the update — the active version stays active.
  • The import preview names the object an Overwrite renames — and warns of a duplicate name.

Operation​

  • A write call without an answer is checked instead of repeated — if unresolved, the operation goes to Clarification as "Write outcome unknown".
  • Update never creates a record — if it is missing in the target system, the operation ends as "Skipped (not present)".
  • If the target system refuses a create, the record is searched once more — a match is updated and shows "Updated (create refused)".
  • A key value from additional data not configured reports "Unknown additional data" — previously a duplicate record or a data error resulted.
  • When a target system asks for a wait, waiting no longer uses up a retry — if it throttles for a whole day, the operation goes to Clarification as "Target system keeps throttling".
  • During a Service Layer outage, a run waits instead of aborting — it shows "Interrupted" and uses no attempt.
  • If the source system rejects the acknowledgment, the run ends as failed — with "Source system rejected the acknowledgment".
  • An incremental run ends with "Change filter does not allow an incremental run" — if the Change filter contains an AND or a linked field.
  • Waiting operations of several routes take turns — one large route no longer crowds out the others.
  • Large runs work through their operations faster — regardless of how many are still waiting.
  • "Last run" and Started show when a run actually executed — a run still waiting shows "Waiting since".
  • Runs with failed operations name a reason — e.g. "Records awaiting clarification", in the tooltip over Last run too.
  • "Overdue" depends on timed runs only — a manually started run no longer hides a missed one.
  • "Event backlog" appears only after four hours without processing — a paused route stays marked as paused.
  • A connection stopped by faults reads "Connection blocked" in Execution — previously "Connection paused".
  • Waiting events loads page by page and holds still while events arrive — Discard all covers events up to loading.
  • An expired sign-in shows "Sign-In Expired" with Reload Page — instead of the notice to reopen the tile.
  • The start page names the reason when the runtime store does not answer at startup — or is newer than the service.
  • Service Layer sessions open on demand — up to Max. Service Layer sessions in the Service Hub, unused ones close after 10 minutes.
  • Error messages from REST target systems name up to three rejected fields — with reason and code.
  • The cleanup is called Report records no longer delivered — in the start dialog too.

Fixed​

Configuration​

  • A required field in a list was lost on save — element fields, additional rows and value lists were affected.
  • Entries were lost on save — among others a transformation's last entered value and a fallback value "Today".
  • A mapping without a selected source became an empty constant value on save.
  • A cleared Time in the schedule was silently saved as 00:00.
  • Saving a Dispatch rule lost every group but the first.
  • Damaged stored content was overwritten — it is now kept, marked "Cannot be read", and the import rejects it.
  • An import created routes twice or did not find a value table — if they were set up separately on both systems.
  • The condition "is empty" missed text fields with empty text — in filters and additional data, "is not empty" wrongly found them.
  • Exclude field on a field of an additional row did not affect change detection.
  • Load by key always read from SAP Business One instead of the route's source.
  • A route with an empty Key field could be activated, and every run failed.
  • Validating and importing large drafts broke off after 30 seconds — they may now take up to five minutes.
  • An endpoint or object without a readable field structure went unnoticed in Validate — now "No readable field structure" appears.
  • REST targets partly found no target fields and Target Path suggestions — for OpenAPI paths with placeholders, value lists and Shopware record paths.
  • Validate missed wrong field references — in list elements, on import routes and in the sub-object link field of additional data.
  • A comparison value using the result of a later step was not reported.
  • After changing the Company database, the connection kept showing the old company's field structure.
  • The configuration comparison showed changes nobody had made — but not a changed Target field or a renamed Target List.
  • Resolved findings stayed — after an autosave as "Changed — check again", after a change until reloading.
  • The Target endpoint picker of a REST connection also offered the login address.
  • An empty retention period field did not show that nothing is deleted — it now shows "never deleted".
  • Minor displays in the checklist, editors and import were wrong — among others "Invalid input" instead of the hint text, and umlauts as character codes.

Operation​

  • With several changes in one run, an outdated state could arrive — older operations now end as "Skipped (stale)".
  • An already written record could count as failed after a timeout — and be created twice when processed again.
  • Key values with special characters such as an apostrophe or "#" missed the target record — multi-part keys too.
  • Export routes into a REST connection did not offer Incremental — runs always read every record, SAP numbers and dates were misread.
  • Leaving the data filter sent unnecessary deletions — records never transferred now end as "Skipped (never transferred)".
  • Deletions without stored data were sent empty — they now go to Clarification as "Deletion without stored record".
  • After a key change in SAP Business One, import routes created a second object mapping.
  • Events behind a paused connection were processed anyway — and failed in the process.
  • An automatic lock later switched a stopped route's automation back on.
  • A target-system search on a number field always failed — effective after the route is activated again.
  • Records filtered out by a condition landed in Clarification — they now end as "Skipped (condition)".
  • An unchanged faulty record failed again in every run — it now ends as "Skipped (clarification open)".
  • A changed schedule started a run right after activation — and wrongly showed the route as "Overdue".
  • After a database fault, a run stayed on "Currently running" for good — it now ends with "Technical fault".
  • A run could not be cancelled while its data fetch waited for a retry.
  • A targeted run waited until a large run's operations were worked through.
  • In Clarification, Close on thousands of entries ran into a timeout — after Reprocess, entries stayed on "Reprocessing".
  • After discarding a draft, every sign-in to a further company failed — until the service was restarted.
  • After a failed license check, processing stopped without notice — within the "Grace period" it now continues.
  • After a pause, "Session Could Not Be Renewed" appeared wrongly.
  • The service shut down when a cancellation hit a running query on SAP HANA.
  • After a database reset, startup waited without notice — it now asks for a Service Layer restart.
  • With many waiting events, the Waiting events dialog stayed empty.
  • Operation detail and Clarification partly showed wrong details — among others the operation's attempts instead of the step's, and an earlier object link.
  • The message for a list field named an internal path — now list, additional row and field as in the mapping.
  • Minor texts and displays were wrong — among others "Source system unreachable" while the source system answered, and a wrapping "Paused (fault)" status.

1.0 · 2026-10-01​

Included components: Service v1.0.0 · UI v1.0.0

At a glance: Validation catches more errors before activation, and Work through checklist leads finding by finding to the place concerned. Runs read more clearly — with four results, running and waiting runs apart, missed executions shown and a reason when no incremental run is possible. The Create or update write path is executable, and Clarification puts both deliveries of a message side by side.

Before you update​

  • ⚠️ Run the database update after updating — the database state in SAP Business One moves from 14 to 23, nothing is processed until then.
  • ⚠️ Leave the payloads folder in the work directory in place — missing files send waiting operations to Clarification.

New​

Configuration​

  • The Create or update write path is executable — the step asks the target system first.
  • Work through checklist — leads finding by finding, across records too, and shows position and status.
  • More checks against the source's field structure — fields in Filter list values and step conditions, Today on non-date fields, an underivable Single-fetch endpoint.
  • Three new findings block activation — duplicate condition identifier, unknown date reference, over-long filter block.
  • Two checks on a step's key source — lookup field outside target schema, row key on composite target key.
  • On Validate, the connection states why its field structure is missing — "Field structure never fetched" leads to Fetch field structure, an unreadable one leaves dependent rules unchecked.
  • A connection names the connected system's date and number format — sample data is checked against it.

Operation​

  • Waiting events of paused routes can be viewed and discarded — through Show events or when switching Automation on.
  • With no incremental run possible, the start dialog and Change filter say why — if the connection lacks setup, Set up now leads there.
  • Missed executions — the status counts executions a still-running route has missed.
  • If the Service Layer is unreachable at startup, a dedicated start screen waits for it.
  • A clarification case puts both deliveries side by side — each readable and downloadable.
  • The Message ID appears in Clarification and History — searchable in History.
  • Three new clarification reasons — "Service Layer gave no cause", an unreadable configuration state and a cancelled operation, previously not closable.

Changed​

Configuration​

  • The Fetch result structure of a REST connection has no defaults any more — fetching routes need Records, further pages and incremental runs Bookmark and Fetch parameter.
  • Two conditions on one relationship path match the same row — previously different ones too.
  • SAP triggers on one object are evaluated separately — a route may have two triggers.
  • The checklist follows the order of the UI — "Resolved" and "Changed — check again" survive a reload.
  • The target key is frozen on activation — the write path no longer reads a foreign schema.
  • Schema findings follow the schema's origin — read by Xchange itself blocks, stored warns.
  • SAP connections judge field structure on Validate like REST ones — permanently unreadable blocks, never fetched warns.
  • A missing Custom procedure reports "No stored procedure with this name was found" — in the checklist too.
  • The mapping test lists failures under "Failed in this test run" — instead of marking editor rows, jumping to the place.
  • Findings in value tables, Mapping and Acknowledgment stay with their row — duplicate table values name every entry.
  • A connection checks a field when you leave it — empty required fields turn red at once, reported together.
  • Markers show the severity as an icon instead of a dot — "Has missing entries" is the third level.
  • Mapping rows show their icons in two fixed places — asterisk for required fields, highlighted gear for further settings.
  • Same as fetch endpoint stays selectable when the fetch endpoint raises no SAP event — a notice says why.
  • The route create dialog offers Dispatch only for Import — Export is no longer locked.
  • An empty Key is prefilled only once the Fetch endpoint is chosen.
  • The key source No external key is now No key.

Operation​

  • A run ends with one of four results — reasons, e.g. "Write conflict", stand beside it, not as a status, also for a run without operations.
  • "Partially succeeded" requires at least one successful record — otherwise "Failed" applies, stored runs included.
  • A paused route or connection starts no run — one used to appear and fail, runs under way wait out the pause.
  • Rejected credentials block the connection during a synchronization too — as already for Drain queue.
  • Execution separates running from waiting runs — waiting ones bundled with count, age and History link.
  • Received messages are stored entirely in the database instead of the payloads folder.
  • Received messages of any size are downloadable — operation details show up to 1 MB in full, then the beginning.
  • A redelivery stays visible — identical as "Skipped (no change)", differing as a clarification case.
  • Clarification and History both show the object key — History also shows the direction.
  • A halted state after a database change names its reason — "Database Change Detected" or "Binding Interrupted".
  • On a failure, the Update history names cause, next step and an error ID for support.
  • A click into the "Operations — last 24 hours" chart filters History — by the clicked series.
  • The service log is quieter and easier to search — lines name operation, run and route, repeated errors appear once.
  • Long spans read in days — e.g. "5 d 13 h" instead of "133 h 36 min", on the key figures too.
  • Presence distinguishes sessions rather than people — including two browser windows of the same person.

Fixed​

Configuration​

  • A trigger with an empty condition field fired on every event of the object.
  • An empty required field did not stop the operation — now "Required field has no value", in mapping tests too.
  • An unreadable value answered every condition with "no" — the record dropped out of the scan range without a trace.
  • A date in a condition was stored in display notation — "01.09.2026" became 9 January.
  • An incompletely translated event filter silently discarded events — Repair event filter now fixes it.
  • Saving replaced a step's unreadable mapping with an empty one — the step now shows a notice with the way out.
  • Unreadable identity fields of a Target system lookup were lost on save — they now stay until you replace them.
  • The import took over unreadable mappings and value-table entries — it now refuses them with the first error.
  • The date reference Today, the Fetch-key field and the Link field (row) of additional data were lost while typing.
  • Picking a field without a date deleted the date reference Today, other references showed as Today — it now stays and is reported as a finding.
  • A list-value filter set by import inside a chain was lost on the next save.
  • A dispatch rule was re-created on every automatic save — when that failed, Behavior when nothing matches was lost too.
  • Waiting changes were lost on a brief Service Layer disruption or a record switch — switching now asks first.
  • A deleted value-table value came back while its save was still running.
  • Save conflicts were handled wrongly — "This record has been modified in the meantime" appeared needlessly, Reload did not discard the waiting save.
  • Additional data on Rows of a list with a Sub-object stayed empty when linked to the Main object.
  • A Single-fetch endpoint misbehaved — wrong records after a Fetch endpoint change, a changed repair path with dispatch input.
  • A value-table entry with surrounding spaces never matched at runtime.
  • An empty Dispatch rule from an import always applied, without "More than one catch-all rule in this route".
  • A Same as fetch endpoint trigger could evaluate a stale object, e.g. after an import.
  • A placeholder with an empty source value sent the operation to Clarification — Validate now reports mistyped paths.
  • Additional data only for row mappings and value tables only in a Fallback value counted as unused and deletable — their absence was not reported.
  • Validate failed after about 30 seconds when a SAP connection lacked sign-in details — the checklist now reports it at the connection.
  • Fetch field structure on a SAP connection failed without recording the failure.
  • Validation reported false, missing or dead-end findings — e.g. "'Field' does not exist in the field structure" or "Identifier used more than once" without a name.
  • Export and the configuration comparison showed a wrong state — the old one for up to an hour after a structural change, chains beside source fields missing.
  • Pickers offered too little or stale entries — SAP endpoints were missing, the field picker showed the previous route's fields.
  • Input fields closed while typing or lost the cursor — e.g. under Replace for Client secret or in a new route's name.
  • Test connection started with an empty Token endpoint, and its result and the duplicate-connection notice stayed.
  • Errors sat out of sight — from Validate, Activate or Discard below a long checklist, now above, from imports below the collision table.
  • Minor displays and interactions in the editors were faulty — e.g. "Validation Outdated", labels in the field tree and the position of an Additional row.

Operation​

  • Drain queue runs kept going or ran twice — a cancelled one consumed messages unprocessed, two drained the same queue.
  • A fetch not matching the Fetch result structure counted as successful — now "Connection does not match the response".
  • Clarification entries were missing or misplaced — an abandoned operation got none, keyless cases fell into one group.
  • A run did not complete its cleanup after a crash — records that left the scope were never withdrawn.
  • A retention period took effect while being typed — a pause while typing "3.5" saved "3".
  • A run could become impossible to finish — if creating its operations aborted, its count stayed at 0.
  • A run whose route or connection was removed meanwhile stayed under "Running now" for good — it now ends with a reason.
  • A Drain queue run beside a synchronization was put back on start.
  • Structural changes failed needlessly or without details — a lost session halted the system with "Missing Permission", errors named no table or field.
  • Service Layer failures were handled wrongly — a failed session pool or connection reset now reports "Service Layer Unreachable".
  • Error messages misled — one wrongly blamed the configuration, a Service Layer rejection showed as an English SAP sentence.
  • An unreachable runtime store made the UI wait for a minute.
  • A run's duration and "Runtime per job" counted a service outage — a run states its active time, with the interruption below it.
  • Periods in History and Clarification left runs out — "Last X Days" without today, a link to a run without older runs.
  • Clarification showed wrong information — the bulk dialog described the opposite, the cause breakdown left rows out.
  • Presence lagged behind — an orphaned entry showed every session as being edited.
  • A language switch missed screens — texts stayed half translated, date and number formats German, the operations chart vanished.
  • Detail columns kept the previous record after a failed load or closed with their message — in Clarification, History and Execution.
  • With the service stopped, lists opened error dialogs, a blocked connection read "Xchange Unreachable" — now "Connection to Xchange Blocked".
  • A route with a dispatch input showed "—" under Next run — and "Runs only manually" in the detail.
  • Empty views showed SAP's default texts — the empty configuration compare also broke its title mid-word.
  • Smaller texts and displays were faulty — e.g. in validation messages, trigger fields, column widths, clarification reasons, transformations, under "Dispatched to" and in messages about the technical user.

0.16 · 2026-09-16​

Included components: Service v0.16.0 · UI v0.16.0

New​

Configuration​

  • Query target of an additional-data query — it reads from the chosen SAP company.
  • The mapping test fetches the additional data live — those at row level too.
  • Write intent and key source per step — Create, Update or both.
  • Condition groups with AND or OR, up to six — three before, fixed to AND.
  • Filtering list values — a summary computes only over the rows that meet its condition.
  • The fallback value has a transformation chain of its own — in the Empty source value tab.
  • Date values in conditions from a calendar — with Today as the reference.

Operation​

  • State, open clarifications and next run per route — eight states from "Operating" to "Cannot be determined".
  • A running run can be cancelled — optionally with Also pause the route.
  • The history shows the object per operation — recorded on creation, not derived from today's route.
  • Every clarification case names its reason — 21 reasons in six cause groups, filterable by group.
  • Clarification cases can be worked in one go — Next case leads to the next open one.
  • A clarification case's block expires after 24 hours.
  • A skipped operation names the clarification blocking it.
  • API reachability can be checked in the Service Hub — with no answer it names the reason.
  • The CSP assistant shows the sources up front — to copy into the Web Client.
  • License statuses "Not verifiable" and "Not checked yet" — a failed check is distinguishable from a pending one.
  • "Run started" appears as a short message instead of a dialog.
  • The Primary step is marked in the history.
  • Schema drift is detected continuously — previously only with the system status open.
  • An unknown database state is named — with the notice to update the Xchange service.

Changed​

  • Execution and history are tidied up — kind, object type and direction sit in the direction icon.
  • A scan over a joined condition ends at its time budget — the next run resumes there instead of reading from the start.
  • A long scan no longer holds up the other requests.
  • The main object list comes from the query target — previously always from your own SAP company.
  • Where the additional data cannot be fetched, the previous test result stands — marked as outdated.
  • Clarification is structured by cause, state and technical details — the list shows Age instead of Failed at.
  • Fallback value and empty behavior are two independent entries — Empty behavior now also offers Transfer unchanged.

Fixed​

Configuration​

  • Saved additional-data queries were lost — a late-loading state overwrote them, and at row level they disappeared entirely.
  • Fallback value and empty behavior were lost on save — on Concatenate and Conditional value mapping.
  • A source value that is explicitly empty was discarded instead of transferred.
  • Conditions over document lines matched the wrong rows.
  • An AND between two condition groups matched nothing.
  • A negated condition on a choice field dropped out of its OR group.
  • Opening a second route took over the fetch endpoint and key of the previous one.
  • A condition dropped while loading shifted the field type of every following one.
  • Picking a sub-object reverted — switching the main object left the entries depending on it in place.
  • Conditions over sub-objects were in part not available at all.
  • A join chain over more than two steps went unanswered — it is now refused on activation.
  • A route with several joined conditions gave no match count — one that could not be determined showed zero as well.
  • A condition on a joined object had no field type.
  • A missing permission emptied the list of fetch endpoints.
  • A connection without a field structure reported a faulty schema — it now shows an empty list.
  • An uncheckable field counted as a missing database column — particularly in document lines.
  • A link field outside the main object was reported as "Not a key field".
  • A source field with a dot in its filter expression counted as missing from the schema.
  • An unreadable date in a filter value surfaced only on Validate — now on every save.
  • Messages on conditions stood at the wrong cell, or twice.

Operation​

  • An API URL set by hand was overwritten by the host name — a path in it disappeared without notice.
  • An unreadable license status prevented the service from starting — a fresh installation also showed two red license notices up front.
  • A structural change could end in a halt with no way out — Finalize structural change had no effect.
  • An outdated default value aborted the entire structural change.
  • Behind a reverse proxy the Web Client refused the tile — the assistant mixed the public address with the internal port.
  • The certificate covered only one of the two host names.
  • Reprocessing a clarification case failed depending on the source system.
  • The automation switch keyed off the wrong permission.
  • An unfinished first installation counted as ready.
  • An update that only caught up on field details forecast no Service Layer restart.
  • The system status was unreachable during a halt.
  • The sign-in connection test failed on a clock running ahead — and a rejection pointed at the identity provider.
  • A started run was missing from "Running now" after an interruption.
  • A rejected single fetch counted as a source-system outage — the message now names key and endpoint.
  • A cancellation gave no reason, and a save conflict claimed another person.
  • An expired login did not point at signing in again.
  • The configuration state in the history showed the product version instead of the run's — and a parked draft could not be restored.
  • The operation header counted an attempt that had not run yet — Avg / attempt showed 0 for it.
  • A run under one second was shown as "0 s" — now as "< 1 s".
  • A setup not yet finished appeared as "v0" — now as "not finalized yet".
  • System status and settings stayed in two columns on narrow screens — with truncated labels.
  • A language switch left text in six lists in the previous language.

0.15 · 2026-09-07​

Included components: Service v0.15.0 · UI v0.15.0

New​

Configuration​

  • SAP Business One as a connection — a second SAP system is connected over the Service Layer.
  • Field structure from OpenAPI — no longer only from OData.
  • Fetch endpoint and target from a list on import routes too — previously only on the SAP side.
  • Fetch result structure per connection — the prerequisite for the incremental fetch.
  • Additional data for rows of a list — a query loads a value for each row.
  • Parent row as a source field — a row of a sub-list reaches the fields of the row it sits in.
  • A filter condition's field type can be declared — where the field structure carries none.
  • A missing field type is filled from the reference data, a contradicting one reported.
  • Today as a filter value — in Source data, Change filter and Event filter.
  • Parked draft — a system reset parks the open draft instead of discarding it.

Operation​

  • Incremental fetch over REST — only what changed, resuming on the next run.
  • All of a route's runs are visible — those currently running and the last five finished.
  • Retention periods in the settings — one period each for events, operations, clarification cases, usage records and the log.
  • An event filter can be corrected while halted too — where it references a field that no longer exists, the configuration stays reachable.

Changed​

  • The field structure sits in the system status, not per route — once for the whole installation, plus per connection.
  • Where the source keeps its own bookmark, there is no change filter.
  • The Operational information names what the next incremental run does — the date it reads from, or the position it resumes at.
  • The Start run dialog opens on Incremental where the route can run one — previously on Full.
  • The Single-fetch endpoint is freely editable where the connection does not derive it.
  • A paused route states its cause — paused by hand or after an error.
  • The navigation shows no counters any more — the open-clarification count stays in Action required, header and screen title.

Fixed​

Configuration​

  • An import discarded the draft before checking it — the decisions are now validated before the draft is replaced.
  • An older route showed neither mapping nor steps — steps from an earlier version are now completed instead of deleted.
  • A date condition compared the time of day too — "is equal to" matched only midnight records, now the day counts.
  • An unreadable date value made event and data filter disagree — it is now refused at check time.
  • Switching the connection left derived details standing — they now follow with the save.
  • A date condition stopped the trigger on SQL Server.
  • A renamed endpoint blocked the connection.
  • An import reported every object as a conflict — a file from an earlier version counts as unchanged again.
  • Permissions did not reach the source and target fields or the mapping.
  • The additional-data fetch demanded a check that had just run.
  • A condition on a joined object counted as faulty.
  • A correct schedule counted as faulty on the Automation tab.
  • A corrected field was flagged again after the save.
  • Picking the same value again triggered a save.
  • Configuration lists lost selection and scroll position on save.
  • The comparison showed technical values — conditions and transformations now appear the way their editor spells them.

Operation​

  • A route stayed blocked after an abort.
  • A faulty additional-data query demanded a Service Layer restart — the halt now states its reason and the structure affected.
  • An unreadable additional-data query failed without a message — it is now reported with its identifier.
  • The SAP error message was missing from the response — a failed step now shows the Service Layer's message.
  • Pausing a route reached open screens only on reload.
  • An originating operation and its repetition were not linked — the cross-link now sits on both sides.
  • A search for a correlation ID returned the whole run — it now leads to the operation it belongs to.
  • The hourly chart hid two thirds of the day — a narrow window now squeezes the 24 columns instead of cropping them.
  • Labels sat offset from their fields in read-only views.
  • Fields in the Start run dialog sat further from the edge than the text beside them.

0.14 · 2026-09-01​

Included components: Service v0.14.0 · UI v0.14.0

New​

Configuration​

  • Field structure of the counterpart — a connection fetches it at a click to fill the field pickers.
  • Compare configuration snapshots — draft against active, or two archived states, per object and field.
  • Restore the previous state — the last archived snapshot becomes active again.
  • Cleanup — after a full synchronization a route reports records outside the data filter, above a threshold only after release.
  • Target system's external key — from a marked mapping row, the response data or a Header.
  • Event type as a source field — for SAP events, Header shows creation, change or deletion.
  • Set operators — is one of and is none of in conditions.
  • Four text transformations — Replace, Trim whitespace, Convert to uppercase and Convert to lowercase.
  • License environment — a transformation yields the licensed environment's identifier, with no source field.
  • The source picker names the step a value comes from.
  • Value tables and object types appear sorted alphabetically for selection.

Operation​

  • Action required on the Overview — open items sorted by urgency, each with a jump target.
  • Operations of the last 24 hours — an hourly bar chart, a click opens that hour's history.
  • Filters and progress in History — filters by status, connection and free text.
  • History detail — shows the received message and, per step, request and response status.
  • Cancel and reprocess operations — History points back to the originating operation.
  • Object ordering — the overtaken operation of a rapidly re-changed record is discarded.
  • Superseded clarifications — a clarification replaced by a newer one gets the filterable status "Superseded".
  • Event backlog — route view and Operational information show pending SAP events.
  • Action required in the header — the number of open items on every screen.
  • Filters in the address — History, Clarification and configuration lists can be passed on with their filters.
  • Deviating database procedure — if it or its permission state deviates, Xchange offers the update.
  • A successful SAP step shows SAP Business One's response status code.

Changed​

  • Addresses survive an activation — bookmarks and jumps out of History stay valid.
  • The connection test now sits under Authentication.
  • Where an update creates structures, Xchange visibly awaits the Service Layer restart.

Fixed​

Configuration​

  • A value typed during a save and the selection were lost, and an open field picker closed.
  • Sum and Count were lost when the field was changed.
  • An empty source field skipped the whole transformation, value table and fallback value included.
  • Conditions evaluated differently per database — text comparisons now respect case, and does not equal covers empty values.
  • The import rejected a bundle exported by Xchange over its format version.
  • Merely viewing created a draft, and closing without a change triggered a save.
  • The mapping showed edited rows and paths incorrectly and locked the toolbar with no step selected.
  • Fetch all could be triggered again while a fetch was running.
  • Fetch field structure gave no feedback, and the old result stayed after a source change.
  • A dispatch rule showed its target routes truncated when reopened.
  • A duplicate route was reported on every opening instead of only when the connection changed.
  • The notice about a configuration changed elsewhere appeared without cause — it now names the change and disappears by itself.
  • The header did not show every draft status and called an edited draft validated.

Operation​

  • When the write to SAP Business One failed, open steps stayed open.
  • On an unknown update step recorded in the database, the service kept working instead of halting.
  • After a skipped run, the route started a full synchronization.
  • After a fault halt, the UI no longer found the service.
  • A run waiting behind a paused route appeared under "Running now" and pushed the history aside.
  • The read-only clamp reached navigation and screens only after a reload.
  • A completed manual review stayed marked as a failure in History.
  • History kept loading without a limit, and grouped lists jumped to the top when refreshing.

0.13 · 2026-08-19​

Included components: Service v0.13.0 · UI v0.13.0

New​

Configuration​

  • Import values — a value table takes pairs from a file or text and replaces or extends the list.
  • Filters on sub-lists and across relationships — for data filters and event conditions, via the field tree.
  • Reload the field structure — a newly created SAP field is then available in the mapping.
  • Three arithmetic transformations — Multiply, Add and Subtract, in the company's decimal separator.
  • Sum and count over a list — sums a field across all rows or counts them.
  • List from a text value — splits a text field into a target list.
  • Negating operators — does not start with and does not contain.
  • Search in the lists — value tables, connections and routes by name and description.
  • Used in routes — value tables and connections link the routes that use them.
  • Description of a connection — the search covers it as well.
  • Jump to the target route — from the dispatch rule's target column.

Operation​

  • Operational information per route — last run and failure, open clarifications, paused automation.
  • Key figures per route — four values over the selected period.
  • Time limit per operation — after a configurable deadline an operation ends as a clarification case.
  • One action for the database update — combines repair and update and lists beforehand what it does.
  • Progress and elapsed time of a running run update without a reload.
  • The automation can be paused and resumed in Execution.
  • Filter History by route — across the route's lifetime, kept when a detail is closed.

Changed​

  • Every validation message leads straight to the place at fault.
  • A record that was only opened is no longer saved.
  • Pasted reference data creates no draft.
  • From 50 mapping rows, Generate mappings automatically warns beforehand with the count.
  • The Update history in System Status is readable at a glance.
  • German texts are set consistently in the UI and the Service Hub.

Fixed​

  • Three controls wrote route configuration without a permission check — AND/OR match, event mode and schedule run type.
  • With large data volumes, a root-relative next page was not requested.
  • The first cycle after the service started ran into nothing.
  • The status display did not restore a lost connection.
  • A failed credential renewal appeared as a generic error — now with its own message, once.
  • List and detail drifted apart — the list now scrolls to the selected row and marks it.
  • A jump to a validation message missed nested tabs, and messages disappeared before their field was corrected.
  • A duplicate value in a mapping was reported per cell instead of as a group.
  • Dialogs opened without input focus — it now sits on the field you start with.
  • A closed clarification case was labelled "rejected" instead of "closed".

0.12 · 2026-08-06​

Included components: Service v0.12.0 · UI v0.12.0

New​

Fixed​

  • During concurrent editing, the second save overwrote the first without notice.
  • Leaving the editor left changes unsaved and the editing marker held.
  • A transfer redirected to a login page counted as successful.
  • Imported records lacked the target environment's timestamp and user.
  • The mapping stopped at 500 rows without notice — it now shows all and opens in seconds.
  • Behind a reverse proxy, saving reported phantom conflicts and the status display dropped after five idle minutes.
  • Conditions offered operators that did not match the selected field's type.
  • The draft validation showed an outdated state, and jumping to a message landed in the wrong place.
  • In SAP Business One 2605, the mapping toolbars were turquoise and navigation entries carried icons.

0.11 · 2026-07-25​

Included components: Service v0.11.1 · UI v0.11.0

Before you update​

  • ⚠️ Run the database update after updating — it moves operation data into the dedicated runtime store.

New​

  • Data origin — chosen explicitly when a route is created, instead of inferred from the trigger.
  • Conditional value mapping — the first matching of several cases supplies the target value.
  • An icon makes each value a field or fixed value — comparing two fields in conditions, fixed text in concatenations.
  • Fixed Rows — a target list can be filled from rows you add yourself.
  • New target route — creates a target route straight from the dispatch rule.
  • SAP reference check — draft validation checks objects and fields against SAP before activation.

Changed​

  • The route editor's tabs follow the data flow — the data source now sits under Source data instead of Trigger, the rest is called Automation.
  • Operation and coordination data live in a dedicated runtime store — this relieves the Service Layer.
  • A mapping row is edited in a dialog — tabs Transformation, Condition, Options, with previous/next navigation.
  • The Additional data section no longer shows the technical query preview.

Fixed​

  • Matching a user table or UDO on a standard field in a data filter prevented activation. (Service v0.11.1)
  • The Service Hub's offline help for the Xchange settings led nowhere.

0.10 · 2026-07-21​

Included components: Service v0.10.0 · UI v0.10.0

New​

  • Parallel processing — multiple transfers run concurrently, and their number can be adjusted without restarting the service.
  • User-defined objects (UDOs) as trigger — besides user tables, UDOs can now raise an event.
  • Cross-entity data filter — source records can be filtered by a reference held in another entity.
  • Step configuration — processing steps can be reordered and given a condition on whether they run.
  • Per-row mapping condition — no longer only at list level.
  • Guided schema update — structural changes on update run with a progress indicator and guided recovery.
  • Connection paused on authentication failure — with a lock marker and notice banner, and transfers to it are rejected.
  • Route editor — a Description field, cron expert mode, and duplicating dispatch rules.

Changed​

  • The UI addresses you formally (German Sie form) throughout.
  • Confirmation dialogs default to Cancel — this prevents accidental confirmation.
  • The mapping test now takes the results of preceding steps into account.
  • The Fetch endpoint picker shows endpoints without the technical prefix, sorted alphabetically.
  • The match count is shown with a thousands separator and a loading indicator while counting.

Fixed​

  • The checklist named only a count instead of the concrete errors and did not jump correctly to the affected field.
  • Sorting in History was erratic and not traceable via any visible column.
  • The Execution list flickered during a running transfer.
  • Sign-in notices, button visibility and input focus were wrong in a few places.

0.9 Pre-Release · 2026-07-01​

Included components: Service v0.9.1 · UI v0.9.1

New​

Setup & operation​

  • Windows service — Xchange runs as a service on a Windows server.
  • Web Client tile — Xchange opens directly in the SAP Business One Web Client.
  • Automatic setup — the service creates its database structure on first start.
  • UNIORG Service Hub — guided setup of the database connection, Service Layer and service parameters.
  • System Status — view operating state and versions, repair the installation.

Security​

  • Single sign-on — sign in via the SAP Business One identity provider.
  • Permissions — access rights via the familiar SAP Business One authorization system.

Configuration​

  • Connections — create and edit REST connections and test the connection.
  • Routes — create and configure export and import routes.
  • Dispatch rules — route incoming documents to the responsible route by rule.
  • Mapping — map source fields to target fields with direct and fixed values, transformations including date and concatenation, and value and object-type lookups.
  • Lists and documents in the mapping — filter and merge list fields, additional lines, multi-step documents, and freely reorderable mapping rows.
  • Enrichment — add further data from SAP Business One to documents during transfer.
  • Value tables — create and maintain.
  • Triggers — manual, scheduled, by event, or by dispatch.
  • Configuration snapshots — validate, activate, export, and import.

Testing​

  • Execution — transfer routes manually for selected records or test them against a pasted sample document.
  • History — follow running and completed transfers, always up to date.
  • Automatic retry — transient issues are retried on their own, and only a final failure sends a transfer to Clarification.
  • Clarification — review failed transfers and reprocess or dismiss them.