1c-cfe-borrow

To borrow 1C configuration objects into an extension, this tool generates borrowed metadata with ObjectBelonging=Adopted and ExtendedConfigurationObject references. It allows you to intercept or modify existing configurations without touching the source ERP config.

Borrowing forms and metadata in 1C extensions creates adopted objects that reference the source configuration. The process registers forms, updates ChildObjects ordering, and propagates metadata across extension components for multiple object types.

Yes, you can automatically borrow referenced resources like pictures and styles from a 1C configuration. The tool optionally auto-borrows these referenced resources from the source configuration when generating extension metadata.

Yes, you need the lxml dependency installed to borrow objects from a 1C configuration into an extension. The tool relies on this library to process and generate the XML metadata required for extension components.

The best way to integrate a legacy ERP object into a 1C extension is running the cfe-borrow tool with ExtensionPath, ConfigPath, and Object parameters. It borrows the desired object to modify behavior or UI without source changes.

When borrowing nested structures and related forms in 1C extensions, limitations include dependency on the source configuration remaining intact for references. Borrowed objects require ExtendedConfigurationObject links to stay valid across extension components.