template-remove

To delete a 1C template safely, you must remove its metadata file and folder while simultaneously updating the root object XML to delete the matching ChildObjects entry, ensuring the metadata registry remains consistent and free of broken references.

After removing a 1C template, MainDataCompositionSchema must be cleared if it still points to the deleted template, preventing dangling schema references during object refactoring and ensuring the 1C configuration directory remains valid.

Yes, you can use Python with the lxml dependency to perform namespace-aware XML editing on 1C configuration directories, executing deterministic file deletion and registry cleanup while preserving the UTF-8 BOM.

Refactoring a 1C processing object requires updating the template metadata file, the template folder within the Templates directory, and the root object XML file together to maintain metadata synchronization during cleanup.

Removing a 1C template requires XML namespace-aware editing that preserves the existing UTF-8 BOM in configuration files, ensuring the 1C platform correctly reads the modified root object XML and ChildObjects registry.

Manually deleting template folders breaks 1C metadata consistency because the root object XML still retains the template's ChildObjects entry, requiring deterministic file deletion paired with automated XML registry cleanup to prevent broken references.