Validate stored dataset JSON and inspect its field tree.

Overview

Validate stored dataset JSON and inspect its field tree. Dataset and mapping work defines the contract between application data and template content. Stable names and representative samples reduce downstream breakage.

Key points

• Validation confirms schema and sample data are parseable JSON.
• The tree endpoint returns the root path and stored schema.
• Version changes should trigger review of affected mappings and templates.
• Validation does not currently replace full business-schema validation.
• Use samples to test required and optional branches.

Recommended procedure

1. Start with representative source data.
2. Define or inspect the dataset tree.
3. Create explicit placeholder-to-XPath mappings.
4. Scan, validate, and test the affected template with missing and repeated values.

Troubleshooting

Validation reports MAPPING_REQUIRED

Create a mapping for every unresolved placeholder and run validation again.

A mapping resolves the wrong field

Look for normalized-name collisions and verify the XPath against sample XML.

An array field is missing from the inferred tree

Use representative sample data with at least one complete array item.

Related documentation

• Map Friendly Placeholders to XPath
• Placeholder Normalization Rules
• Resolve Missing Field Mappings

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.