meta-remove

To safely delete a metadata object from a 1C configuration dump, you remove it from Configuration.xml, clean subsystem references, and delete the corresponding object files. Reference scans across XML and BSL files block unsafe deletions unless forced.

Checking for BSL references before removing a 1C metadata object involves scanning XML and BSL files for existing links to the target. The process detects references and blocks deletion unless you explicitly use the Force flag to override.

Yes, you can preview metadata removal from a 1C configuration without deleting files by using the DryRun flag. It simulates the removal process to show what would happen, and the KeepFiles flag offers deregistration-only mode without physical file deletion.

Safe deletion in a configuration XML dump supports removing various 1C metadata types including Catalog, Document, modules, reports, registers, plans, roles, and forms by deregistering them in Configuration.xml and cleaning subsystem references.

1C metadata removal fails when existing references are found in subsystems to prevent accidental breakage. The process scans for links in XML and BSL files and blocks deletion to ensure safe refactoring unless you explicitly apply the Force flag.

Yes, meta-remove requires parsing Configuration.xml in MDClasses or V8 namespaces for 1C refactoring. This parsing is essential to deregister objects from ChildObjects and accurately clean subsystem references during the metadata removal process.