validate

You can validate 1C metadata XML by running type-specific structural checks on configuration files, extensions, forms, and roles to catch broken links and missing blocks before compilation.

You can check configuration files, extensions, managed forms, subsystems, command interfaces, roles, DCS schemas, spreadsheet layouts, and external EPF/ERF files for invalid UUIDs and duplicate identifiers.

To check 1C external EPF and ERF files for structural errors, run a validation script that parses XML structures, verifies required blocks, and returns a pass/fail result with error counts.

Yes, you can validate DCS schemas and spreadsheet layouts by mapping the object type to a specialized validator script that checks nested structures and cross-references for consistency.

Your 1C configuration breaks after manual XML edits due to broken links, missing required blocks, or inconsistent nested structures that structural validation can detect before building.

Yes, you need to provide the ObjectType and ObjectPath parameters so the validator can map the object type to the corresponding PowerShell script and return a clear pass/fail result.