What problem does it solve? Building OmniDataTransform (ODT) mappers by hand is error-prone: dot notation breaks SOQL generation, missing OutputObjectName silently drops items, and uneven hierarchy depths flatten unpredictably. This Skill provides the rules, validation workflow, and scripts to author correct Extract and Transform ODTs and debug empty or malformed output. ## 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 docgen_odt_validate.py, docgen_odt_inspect_hierarchy.py, and docgen_odt_execute.py to catch null fields, duplicate sequences, and depth-uniformity violations before execution. - Debugging and Comparison: Compares ODT revisions and executes Extracts against live records to confirm output JSON shape. - Use Case: You need an Extract ODT that pulls a Quote and its line items into nested JSON for a proposal document. Use this Skill to model the hierarchy, validate it, and execute it against a scratch org before wiring it into a template. ## Quick Start Ask the agent to create and validate an Extract OmniDataTransform for the Quote object and run it against a record in your scratch org.
