meta-remove

Yes, you can deregister a catalog from a 1C configuration by providing the configuration directory path and the object identifier. The operation checks for linked references in code and metadata before safely removing the catalog.

Yes, you can perform a dry run to preview metadata deletion changes before they are applied. This allows you to verify which objects and linked references will be removed from your 1C configuration directory safely.

Yes, removing deprecated metadata includes reference checks to prevent broken links. The skill scans your 1C configuration for code and metadata dependencies linked to the object before completing the deletion process.

You need the specific configuration directory path and the target object identifier to remove a document or register. This information allows the skill to locate the metadata and verify no linked references remain before deletion.

Metadata removal in a 1C configuration may fail or halt if linked references are detected in associated code or other metadata objects. The skill requires resolving these dependencies first to prevent broken references and maintain integrity.