1c-db-dump-xml

Export 1C configurations to XML files using the 1cv8 executable.

40|11|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-db-dump-xml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-db-dump-xml
Source: https://github.com/Desko77/claude-code-skills-1c/tree/main/skills/1c-db-dump-xml
Command: npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-db-dump-xml

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Exports 1C configurations to XML files for source control, auditing, and backup, enabling external tools to work with 1C metadata.

Core Features & Use Cases

  • Full, Changes, Partial, and UpdateInfo dump modes to cover typical workflows.
  • Works with both file-based infobases and server-based deployments via the 1cv8 interface.
  • Use Case: Prepare an XML dump of your configuration to review changes or feed a CI/CD pipeline.

Quick Start

Run the db-dump-xml script to export your configuration to an XML folder from the command line.

Frequently Asked Questions about 1c-db-dump-xml

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

FAQPage Schema
How do I export a 1C configuration to XML files from the command line?

Export 1C configurations to XML files by running the db-dump-xml script, which invokes the 1cv8 executable to dump metadata into a configurable output directory. You can automate this process for source control, backup, or CI/CD integration workflows.

What dump modes are available when exporting 1C metadata to XML?

1C metadata XML dump modes include Full, Changes, Partial, and UpdateInfo. These modes cover typical workflows, allowing you to export the entire configuration, capture incremental updates, dump specific sections, or update only the ConfigDumpInfo.xml file for auditing.

Does the 1C XML export script work with server-based infobases?

Yes, the 1C XML export script works with server-based deployments using InfoBaseServer and InfoBaseRef parameters. It also supports file-based infobases via InfoBasePath, requiring the 1cv8 executable to interface with your target environment.

What do I need to set up before dumping 1C configurations to XML?

Dumping 1C configurations to XML requires the 1cv8 executable and connection parameters like V8Path alongside either InfoBasePath for file-based infobases or InfoBaseServer and InfoBaseRef for server-based deployments to target your environment correctly.

When should I use incremental XML dumps for 1C configurations?

Use incremental XML dumps for 1C configurations when you need to capture only recent metadata changes rather than performing a full export. The Changes mode updates the ConfigDumpInfo.xml and outputs modified files, optimizing source control tracking and CI/CD pipeline integration.

Can I update only the ConfigDumpInfo.xml without exporting the full 1C configuration?

Yes, you can update only the ConfigDumpInfo.xml using the UpdateInfo dump mode. This allows you to refresh the metadata audit tracking file without performing a full or partial XML export of the entire 1C configuration.