Create a reusable description of the data a template expects.

Overview

Create a reusable description of the data a template expects. Dataset and mapping work defines the contract between application data and template content. Stable names and representative samples reduce downstream breakage.

Key points

• A dataset has a tenant owner, name, caption, description, and root path.
• Schema and sample data are stored as JSON text.
• The default root path is /data.
• Datasets are versioned as they change.
• Templates and components may reference a dataset UUID.

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

• Infer a Dataset from Sample Data
• Validate and Browse a Dataset
• Map Friendly Placeholders to XPath

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.