What problem does it solve? OmniDataTransform (ODT) mappers fail silently when items lack OutputObjectName, use dot notation, or form depth-uneven hierarchies, producing empty output or malformed arrays that are hard to diagnose. This Skill provides the rules, validation scripts, and debugging workflow to author correct Extract and Transform ODTs. ## Core Features & Use Cases - ODT Design Rules: Enforces colon-path notation, mandatory OutputObjectName, and separation of object-query hierarchy from field-mapping output shape. - Validation and Inspection: Runs scripts to catch null fields, duplicate sequences, dot-notation misuse, and visualize hierarchy trees with depth-uniformity checks. - Execution and Comparison: Executes Extract ODTs against live records and compares ODT revisions before wiring them into document templates. - Use Case: When a Quote proposal extract returns empty JSON, use the inspect-hierarchy and execute scripts to locate the malformed item, fix the mapping, and confirm the output shape. ## Quick Start Ask the agent to validate and execute the ODT named RLMQuoteProposalExtract against a record in your dev-scratch org and report any hierarchy or mapping errors.
