Elysia Tools
Navigation
Workflow Playbook
Extract selected JSON fields by path, reshape the payload with JSONata, and record field-level provenance without claiming business-semantic validation.
Hubs
This workflow is for data engineers, integration developers, and analysts who need a transformed JSON payload that another person can inspect. Start with one representative input sample, a short list of requested fields, and an output sample or target shape. Keep the original input unchanged. Decide how missing paths, nulls, arrays, and derived values will be counted before running the tools.
Use JSONPath Query Tool to locate the source paths and count what was requested, matched, empty, or missing. This makes a path mistake visible before it is hidden inside a larger expression. Move to JSONata Query & Transform Studio only after the selected values are understood. Record the expression and compare its output with the expected sample, paying attention to renamed keys, nested objects, filtered items, and calculated fields.
Use JSON Data Lineage Tracer to connect each output field to a source path or to the dependencies used to derive it. The acceptance packet should contain the input sample, the transformed output sample, the field counts, the JSONata expression, and a coverage statement for every output field. Missing or unresolved paths stay visible as gaps. The result documents transformation provenance; it does not promise that the business interpretation or downstream application is correct. For adjacent formatting or file conversion work, see JSON Format and JSON Convert.
Workflow playbook
Open the representative payload, identify object and array boundaries, and list the fields that the output is expected to contain before writing the transformation.
Run the JSONPath expressions, save the matched values, and record requested, matched, empty, and missing counts so selection errors are visible.
Apply the JSONata expression to the selected data, compare the result with the expected output sample, and note renamed, filtered, nested, or derived fields.
Build the field-level lineage record from input paths through the JSONata step to output fields, then check lineage coverage and preserve unresolved gaps for review.
Use JSONPath Query Tool when you need to locate or count source values by path. Use JSONata Query & Transform Studio when the selected values must be renamed, nested, filtered, or combined into a new payload.
Define this before transforming. A directly copied field should keep its source path, a calculated field should list its dependencies and expression, and an absent field should remain an explicit missing result rather than being invented.
Require an input/output sample pair, a count of requested and produced fields, and lineage coverage for every output field before accepting the transformation record.