View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000039 | Inlyra Studio | Input Tools | public | 2026-09-20 02:30 | 2026-09-20 02:30 |
| Reporter | inlyradev | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Target Version | v1.1.0 | ||||
| Summary | 0000039: Add XML Input and Output Tools | ||||
| Description | Add native XML Input and XML Output tools to Inlyra Studio for reading, transforming, and writing XML data. XML is hierarchical rather than inherently tabular, so the tools should provide a practical method of converting repeating XML elements and attributes into Inlyra workflow rows and columns. XML Input The XML Input tool should support: Reading .xml files. Selecting the repeating XML element representing workflow records. XPath or similar record-path selection. Reading element values. Reading XML attributes. Nested elements. Repeating child elements. Field discovery and selection. Automatic data-type inference where practical. Preview of the resulting dataset. Handling optional/missing elements. Clear errors for malformed XML. Example source: <customer name="Acme"> <orders> <order id="1001" amount="250" /> <order id="1002" amount="400" /> </orders> </customer> Possible configuration: Record Path: /customer/orders/order Fields: @id @amount Parent Fields: customer/@name Expected output: customer | id | amount Acme | 1001 | 250 Acme | 1002 | 400 The design should clearly distinguish between: Elements Attributes Repeating elements Parent/context values XML Output The XML Output tool should support: Writing .xml files. Configurable root element name. Configurable row/record element name. Writing workflow fields as child elements. Proper XML escaping. Handling null/missing values. Optional formatted/indented output. Overwrite behavior consistent with other Inlyra Output tools. For example, a configuration could specify: Root Element: orders Record Element: order and produce: <orders> <order> <customer>Acme</customer> <id>1001</id> <amount>250</amount> </order> <order> <customer>Acme</customer> <id>1002</id> <amount>400</amount> </order> </orders> Advanced hierarchical XML construction, namespaces, schemas/XSD, and complex parent/child grouping can be considered separately rather than blocking initial XML support. Design Notes: JSON and XML should ideally share an internal hierarchical-data mapping architecture where practical. Concepts such as record-path selection, field discovery, flattening, parent/context fields, preview, and type inference should behave consistently between the two formats. | ||||
| Tags | No tags attached. | ||||
| Report Type | Feature Request | ||||
| Edition | Both | ||||
| Operating System | Windows 11 | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-09-20 02:30 | inlyradev | New Issue |