Skip to main content

Version 1.18.2.11

Release Date: September 21, 2026 Release Type: Stable Previously published as: 1.18.27 (image tag staging-1.18.27)

OData connector corrections across the designer and the runtime — typed filter literals, valid $batch, $count and $value requests, and working delta reads — together with graphical mapping fixes for target schemas uploaded as sample XML.

Backend Server​

New Features​

  • OData: expressions resolved across the whole address, and typed key values: Simple expressions such as ${exchangeProperty.x} are now resolved anywhere in an OData address, including inside $filter, where they previously reached the service unresolved. Key values are sent in the typed form the designer renders (quoted strings, guid'...'), so reads by key are no longer rejected by the service.

Bug Fixes​

  • OData delta reads without query options work: A delta read on an entity with no filter, sort or field selection produced a malformed query and failed on every attempt. The delta condition is now appended correctly.
  • OData Batch Processing sends a valid $batch request: With Batch Processing enabled, the connector only appended $batch to the entity path, which services reject. It now posts a proper multipart batch request to the service root and places write operations inside a changeset. Each batch carries one operation.
  • Graphical mapping reproduces the root, element order and namespaces of a sample-XML target: When the target schema was uploaded as a sample XML document, the output was wrapped in a generic <root> element and child elements followed the order in which the mapping lines were drawn, so a partner could reject a message that was reported as successful. The output now uses the sample document's own root element, element order and namespace declarations. In addition, collections declared in an XSD or sample-XML target stay collections even when they are empty or contain a single element.
  • Flow simulation no longer times out on a busy server: The simulation time limit is raised from 30 to 120 seconds. Heavy flows simulated while the server was under load were cut off and shown as failed with zero steps, although the flow itself was correct.

Frontend Server​

Bug Fixes​

  • OData Start node headers and key value are saved: Headers entered on the OData Start node were silently dropped when the flow was saved, and the key value could not be stored as entered. Both are now stored with the flow, together with the count and value settings and the selected metadata resource.
  • OData $value address survives saving: The key and the property that make up a $value address are now stored with the flow. Previously they were lost on save, so reopening the flow rebuilt an address that no service resolves.

Frontend Web​

New Features​

  • OData filter values rendered as typed literals: Filter values are now written into $filter according to the type of the field: dates as datetime'...' on OData v2/v3 and in ISO form on v4, GUIDs as guid'...', and strings in quotes. The field type is stored with each filter row, so the query is built correctly even when the service metadata is not available, for example in a copied flow.
  • OData panel usability: The entity list is reloaded when the selected connection changes instead of keeping the entities of the previous service, and long field lists collapse behind Show Fields / Show Query Fields.

Bug Fixes​

  • OData $count and $value build valid requests: The count option is now written per OData version ($count=true on v4, $inlinecount=allpages on v2/v3) instead of a bare $count that services reject. $value is now built as a path (Entity(key)/Property/$value); the panel asks for the key and the property as soon as the switch is on, and both are required.
  • OData $orderby and multi-row filters: Multiple sort fields are now separated by commas, and filter rows with no condition selected are joined with and instead of being glued into one invalid expression.
  • Selected OData fields get a placeholder matching their type: Select Fields now adds numeric fields to the request body as 0 and boolean fields as false instead of empty strings, which services reject for non-string properties. This applies to both the OData Start node and the OData receiver node.
  • OData validation catches missing credentials and incomplete filter rows: The OData receiver node now requires a credential when Basic or OAuth2 authentication is selected, and the OData Start node requires every filter row to have a field, an operator and a value. Previously such flows could be saved and deployed and then failed at runtime.
  • Deleting a node no longer blocks Save: After deleting a node that had conditionally required fields filled in — for example Basic authentication with a credential, or filter rows — Save could be refused with validation errors for the node that no longer existed. Leftover form entries of deleted nodes are now discarded before validation.
  • Graphical mapping keeps the root element of a sample-XML schema: A schema uploaded as a sample XML document now shows the document's root element as the top node of the tree, the same shape XSD schemas have. Mappings saved under the previous shape are re-linked automatically when opened, in the editor and in the read-only trace viewer; nothing is rewritten until you save.

1.18.2.11 is a stable release. Previous: 1.18.2.10