Checks the package model, the metadata object, and its relationship with the configuration.
Each finding is output on a separate line with an explanation. Exit code 1 on errors.
Parameters
| Parameter | Required | Description |
|---|---|---|
PackagePath |
yes | Package directory, Ext/Package.bin or <Имя>.xml of the metadata object. Alias — -Path |
ConfigDir |
no | Root of the sources. By default determined by the package location |
Detailed |
no | Show successful checks, not only problems |
MaxErrors |
no | Stop after N errors. Default 20 |
OutFile |
no | Write the report to a file |
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/xdto-validate.ps1" -PackagePath "<путь>"
[ERROR] — the platform will not accept such a package or will accept it incorrectly.
[WARN] — the package is functional, but there is a risk worth knowing about.
Why run it if the package already loads
The platform does not diagnose some defects: it silently replaces an unresolved type from a foreign namespace
with xs:anyType, and the package appears loaded until
ФабрикаXDTO returns an unstructured value at runtime. Such things are visible only
statically — before loading into the database.
Typical workflow
/xdto-compile,/xdto-editor rework via/xdto-decompile→/xdto-compile -Force/xdto-validate <путь>— before loading into the database/db-load-xml+/db-update