Diagnose and correct MAPPING_REQUIRED validation results.

Overview

Diagnose and correct MAPPING_REQUIRED validation results. Dataset and mapping work defines the contract between application data and template content. Stable names and representative samples reduce downstream breakage.

Key points

• Scan identifies placeholder text and its location.
• Validate compares scanned placeholders with known mappings.
• Create or update mappings for every unresolved required field.
• Recompile after mappings are corrected.
• Do not bypass missing fields by editing compiled artifacts directly.

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

• Placeholder Normalization Rules
• Map Friendly Placeholders to XPath
• Validate and Browse a Dataset

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.