1c-meta-remove

To safely remove metadata objects from a 1C configuration dump, the script scans XML and BSL files for references, deregisters the object from Configuration.xml, cleans subsystem content, and deletes files when allowed to prevent broken configurations.

When deleting a 1C metadata object, the script automatically cleans up related subsystem Content entries to ensure no broken references are left behind in the configuration dump.

You can test metadata removal from 1C configurations safely by running the script with the -DryRun switch, which reports intended outcomes without modifying or deleting any files.

Yes, the script supports removing multiple 1C object types by mapping each object type to its corresponding directory and scanning the configuration dump for all related XML and BSL references.

To force delete 1C metadata files, you can use the -Force switch to override standard safety checks, or use -KeepFiles to deregister the object from Configuration.xml while preserving the actual files on disk.

1C configurations break during manual metadata deletion because leftover references in XML and BSL files remain uncleaned, which the script prevents by scanning and deregistering objects from Configuration.xml.