What problem does it solve? OmniDataTransform (ODT) mappers fail silently when items lack OutputObjectName, use dot notation, or have uneven hierarchy depths, producing empty output or malformed arrays that are hard to diagnose. This Skill provides the rules, validation workflow, and scripts to author and debug ODTs correctly. ## Core Features & Use Cases - ODT Authoring Rules: Enforces colon-path notation, mandatory OutputObjectName, and separation of object-query items from field-mapping items. - Validation and Inspection: Runs scripts to validate metadata, visualize hierarchy trees, check depth uniformity, and execute Extracts against live records. - Comparison and Debugging: Compares ODT revisions and diagnoses empty output or malformed JSON arrays. - Use Case: When a Quote proposal Extract returns empty results, run the validate and inspect-hierarchy scripts to find a missing OutputObjectName or a depth-uneven branch, fix the item, and re-execute against a record ID. ## Quick Start Ask the agent to validate and inspect the hierarchy of your OmniDataTransform, then execute it against a record ID in your scratch org to confirm the output JSON shape.
