cfe-validate

To validate a 1C configuration extension, parse the extension directory or Configuration.xml file to check root structures, namespaces, UUIDs, and required properties for structural correctness. This confirms metadata integrity and catches missing files or broken references before deployment.

1C CFE metadata validation checks extension packaging, XML structure, and object-reference consistency. It verifies required namespaces, UUIDs, child objects, borrowed objects, enum values, forms, and directories to ensure configuration fields are valid.

Yes, you can use lxml to inspect 1C extension XML files. The validation logic relies on lxml for deterministic file parsing to confirm required namespaces, UUIDs, child objects, and related metadata files within the CFE package.

You need to check borrowed object integrity in a 1C extension after creating or editing the configuration. This detects broken references, verifies child objects and form dependencies, and ensures metadata consistency before packaging the CFE.

1C extension structural errors occur when XML root structures, namespaces, or UUIDs are invalid or missing. Applying extension XML validation detects broken references, missing files, and invalid configuration fields introduced during edits.