meta-remove

To safely delete 1C metadata objects, use a reference-aware removal process that scans XML and BSL code for usages, blocking deletion if references are found. It also cleans Configuration.xml and subsystem content recursively.

Cleaning up obsolete 1C catalogs and documents is best handled by removing the object's XML and folder while deregistering it from Configuration.xml and subsystem Content entries. This ensures the configuration dump remains valid without leftover references.

Yes, you can deregister a 1C metadata object from Configuration.xml without deleting files by using a KeepFiles mode. This removes the object from ChildObjects and subsystem Content entries while preserving the original XML and folder structure on disk.

Reference checking for removing BSL modules and roles scans XML and BSL code for blocking patterns that indicate the target object is still in use. If references are detected, the removal is blocked unless a Force mode is applied to override the safety check.

Yes, 1C metadata deletion supports a DryRun mode to preview changes before modifying the configuration dump. This allows you to verify which objects, Configuration.xml entries, and subsystem content will be affected without committing any actual file deletions.