1c-cf-validate

To validate a 1C Configuration.xml, run the cf-validate script with the config path parameter. It checks XML well-formedness, InternalInfo, language definitions, and object directories to ensure metadata integrity.

1C configuration validation checks InternalInfo for 7 ContainedObject entries, missing ClassIds, and verifies Properties like Name, DefaultLanguage, and RunMode for consistency and proper metadata definitions.

Yes, you can validate a directory by pointing the config path parameter to a directory containing Configuration.xml. The validation tool will automatically locate and verify the file structure and object directories.

Yes, you need the lxml dependency installed to check 1C Configuration.xml well-formedness and enum values. The validation script relies on this library to parse and verify XML structure and property consistency.

1C configuration validation fails on missing Language files because the tool enforces checks for deployed configurations, ensuring that all language definitions have corresponding files and object directories exist to maintain metadata integrity.

To output detailed validation results for a 1C Configuration.xml file, use the optional detailed output parameter and specify an OutFile. This provides an extended report of the InternalInfo, object types, and enum property checks.