News and Alerts
Breaking Change in Experlogix Documents 1.0.0.preview28: Child Form Data Schema Update
February 26th, 2026
Summary
Starting with Experlogix Documents version 1.0.0.preview28, a breaking change has been introduced in the output data schema of form data sets that contain child forms.
This change affects how child form data is exposed in the generated data structure and may impact existing downstream mappings in Smart Flows templates, flows, and other integrations.
Customers upgrading to this version must review and update affected mappings to ensure continued correct behavior.
What changed?
In versions prior to 1.0.0.preview28, the output data schema of a form containing a child form included an extra <data> element at the root of the child form structure.
As of version 1.0.0.preview28, this <data> element has been removed.
Before (earlier versions)
<childForm>
<data>
<field1>...</field1>
<field2>...</field2>
</data>
</childForm>
After (1.0.0.preview28 and later)
<childForm>
<field1>...</field1>
<field2>...</field2>
</childForm>
The child form fields are now exposed directly under the child form node, without the intermediate <data> element.
Impact
This change impacts all references to child form fields that rely on the old schema structure.
You may be affected if you reference child form data in any of the following:
-
Smart Flows templates (data mappings, expressions, conditions)
-
Smart Flows flows (data mapping, conditional logic, metadata mappings)
-
Integrations or custom logic that consume submitted form data
-
Any downstream processing that assumes the presence of a
<data>element
If mappings are not updated, affected fields may:
-
Resolve to empty values
-
Cause validation errors
-
Break downstream logic
Required action
Update downstream mappings
To mitigate the impact of this change, all downstream mappings that reference child form fields must be updated.
Specifically:
-
Remove the
.datalevel from field references -
Update mappings to reference child form fields directly
Example mapping update
Before
childForm.data.field1
After
childForm.field1
Apply this update consistently across:
-
Templates
-
Flow blocks
-
Conditions
-
Metadata mappings
-
Any other location where child form data is referenced
Why this change was made
Removing the extra <data> wrapper simplifies the data schema, improves consistency with parent form structures, and reduces unnecessary nesting. This results in cleaner mappings and a more predictable data model going forward.
Version information
-
Introduced in: Experlogix Documents 1.0.0.preview28
-
Change type: Breaking change
-
Affected area: Form data set output schema (child forms)
Recommendation
Immediately after the upgrade to 1.0.0.preview28, we recommend:
-
Identifying all templates, flows, and integrations that reference child form data
-
Updating mappings to reflect the new schema
-
Testing affected flows and document generation scenarios.