meta-validate

Validating 1C metadata involves inspecting MetaDataObject XML against allowed types and internal rules. The tool checks root structure, GeneratedType blocks, and Properties to catch configuration issues before deployment using the lxml dependency.

GeneratedType consistency checking verifies internal XML blocks within 1C metadata objects against defined schemas. It ensures standard attributes, child object rules, and UUID formats conform correctly, preventing structural errors during configuration.

Yes, you can validate multiple 1C metadata objects in batch mode. The validator supports batch processing via pipe-separated file paths, allowing simultaneous verification of name uniqueness and cross-object rules across several XML files.

Yes, the validator comprehensively checks standard attributes and child objects in 1C XML. It inspects Properties like Name and Synonym, and verifies allowed ChildObjects to ensure complete metadata integrity and schema compliance.

To check UUID presence and name uniqueness in 1C metadata XML, run the validator to inspect cross-object rules. It verifies UUID formats and name conflicts, generating detailed or concise reports to identify structural remediation needs.

Limitations of validating 1C metadata via XML schema checks include requiring the lxml dependency and strict adherence to predefined MD schema rules. The validator focuses purely on structural integrity rather than underlying business logic correctness.