View Issue Details

IDProjectCategoryView StatusLast Update
0000038Inlyra StudioInput Toolspublic2026-09-20 02:28
Reporterinlyradev Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Target Versionv1.1.0 
Summary0000038: Add JSON Input and Output Tools
DescriptionAdd native JSON Input and JSON Output tools to Inlyra Studio for reading, transforming, and writing JSON data.

JSON support should accommodate both simple flat JSON structures and nested/hierarchical data commonly encountered in application exports, API responses, configuration data, and data integration workflows.

JSON Input

The JSON Input tool should support:

Reading .json files.
JSON arrays containing multiple records.
Single JSON objects.
Nested objects.
Nested arrays.
Selection of a record path identifying which array/object represents workflow rows.
Field discovery and selection.
Automatic data-type inference where practical.
Preview of the resulting tabular dataset before workflow execution.
Flattening nested objects into columns.
Expanding arrays/repeating structures into rows where appropriate.
Handling missing/null properties.
Clear errors for malformed JSON.

Example source:

{
  "customer": "Acme",
  "orders": [
    {
      "id": 1001,
      "amount": 250
    },
    {
      "id": 1002,
      "amount": 400
    }
  ]
}

Possible configuration:

Record Path: $.orders

Fields:
id
amount

Parent Fields:
customer

Expected output:

customer | id | amount
Acme | 1001 | 250
Acme | 1002 | 400
JSON Output

The JSON Output tool should support:

Writing .json files.
Writing workflow rows as a JSON array.
Configurable pretty/indented vs. compact output.
Proper handling of strings, numbers, Boolean values, dates, and nulls.
Correct JSON escaping.
Optional overwrite behavior consistent with other Inlyra Output tools.

Initial JSON Output can focus on producing a straightforward array of objects:

[
  {
    "customer": "Acme",
    "id": 1001,
    "amount": 250
  },
  {
    "customer": "Acme",
    "id": 1002,
    "amount": 400
  }
]

Advanced construction of deeply nested JSON structures can be considered separately for a later release rather than blocking initial JSON support.

Design Notes:

JSON parsing should be designed with future HTTP/API Input functionality in mind. The same JSON parsing/flattening engine should eventually be reusable for JSON returned by REST APIs rather than being coupled specifically to files.
TagsNo tags attached.
Report TypeFeature Request
EditionBoth
Operating SystemWindows 11

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-09-20 02:28 inlyradev New Issue