cfe-borrow

Borrowing 1C configuration objects into an extension requires validating object syntax from source Configuration.xml paths and generating adopted XML metadata. This preserves metadata consistency while supporting catalogs, documents, enums, and common modules for extension workflows like method interception.

Copying managed forms during 1C object borrowing is supported. The process registers borrowed forms under the parent object and optionally includes main-attribute borrowing, enabling editable form data paths for later modification directly within the extension.

You can adopt catalogs, documents, enums, common modules, and registers into a CFE extension. The borrowing process generates adopted XML metadata with child-object registration, preserving dependency consistency for related common pictures and style items referenced by forms.

Yes, lxml is required as a dependency to process XML metadata when adopting 1C configuration objects into extensions. The tool parses source and extension Configuration.xml paths, validates object syntax, and generates adopted XML metadata using this library.

To add new attributes to existing 1C objects, borrow the object and its main attributes into the extension first. The generated XML metadata registers the parent object and enables form changes, allowing you to expose new attributes on the extension form.

When borrowing 1C forms, related common pictures and style items are automatically handled to maintain extension consistency. However, you must provide valid source and extension Configuration.xml paths, as invalid object syntax will fail validation during the borrowing process.