cfe-borrow

Borrow 1C configuration objects into an extension with adopted metadata.

41|5|Updated May 28, 2026

Search Tags:#configuration #extension #forms #borrowing #1c #cfe-borrow

Ready to run

npx skills add https://github.com/msrv-tech/skills --skill cfe-borrow-msrv-tech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cfe-borrow
Source: https://github.com/msrv-tech/skills/tree/main/cfe-borrow
Command: npx skills add https://github.com/msrv-tech/skills --skill cfe-borrow-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the process of borrowing 1C configuration objects into an extension, eliminating manual duplication of metadata and forms when adapting configurations.

Core Features & Use Cases

Borrow individual objects such as Catalogs, Documents, Enums, and more into an extension, creating adopted metadata and updating extension ChildObjects.
Borrow multiple objects in a single run and automatically register borrowed forms in the target extension.
Auto-borrow related resources (like common pictures or styles) when encountered in the source configuration, reducing manual coordination.

Quick Start

Run the cfe-borrow script with -ExtensionPath pointing to your extension and -ConfigPath to your 1C configuration, then specify -Object with one or more objects to borrow.

Frequently Asked Questions about cfe-borrow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I borrow 1C configuration objects into an extension without manual duplication?▼

To borrow 1C configuration objects into an extension, run the cfe-borrow script with -ExtensionPath and -ConfigPath parameters, specifying target objects via -Object. This automatically copies metadata, sets ObjectBelonging=Adopted, and updates extension ChildObjects safely.

Can I borrow multiple 1C objects and their forms into an extension in a single run?▼

Yes, you can borrow multiple 1C objects into an extension in a single script execution. The process automatically registers borrowed forms in the target extension and auto-borrows related resources like common pictures or styles encountered in the source configuration.

What parameters are required to copy 1C metadata into an extension using a script?▼

The required parameters to copy 1C metadata are -ExtensionPath pointing to your extension, -ConfigPath to your 1C configuration, and -Object specifying the objects to borrow. An optional -BorrowMainAttribute parameter is also available for specific use cases.

Does borrowing 1C configuration objects update the extension ChildObjects tracking automatically?▼

Yes, borrowing 1C configuration objects updates the extension ChildObjects tracking automatically. The script reads source configuration metadata, generates new XML entries, and safely updates the extension metadata to integrate the adopted objects seamlessly.

What is the best way to adapt 1C configurations by adopting catalogs and documents into extensions?▼

The best way to adapt 1C configurations is using an automated borrowing script that copies individual objects like Catalogs, Documents, and Enums into an extension, creating adopted metadata while eliminating manual coordination of common resources.