xdto

Inspect and apply targeted mutations to 1C XDTO package schemas via MCP tools.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill xdto-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: xdto
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/xdto
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill xdto-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing 1C XDTO packages (such as EnterpriseData exchange schemas) by hand is error-prone: the binary Package.bin layout, XML namespaces, and QName prefixes make direct edits risky. This Skill provides a controlled way to read an XDTO package by logical address and apply precise, previewed mutations through the unica MCP server. ## Core Features & Use Cases - Schema inspection: Read any XDTO package via unica.xdto.info using a logical metadata path like XDTOPackage.EnterpriseData_1_17_3, without touching internal platform files. - Safe point mutations: Add or remove value types, object types, and properties (including nested anonymous types via propertyPath) with unica.xdto.edit, always previewed with dryRun: true before applying. - Byte-level fidelity: The writer preserves BOM and observed line endings, returns no-op on repeated additions, and rejects ambiguous QName prefix mappings instead of guessing URIs. - Use Case: Extend an EnterpriseData exchange schema by adding a new property Документ_НовыйДокумент to the ЛюбаяСсылка type, preview the exact change, and apply it only after user confirmation. ## Quick Start Ask the assistant to show the structure of the XDTO package EnterpriseData in your 1C source set, then request a preview of adding a new property to a specific type before confirming the change.

Frequently Asked Questions about xdto

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

FAQPage Schema
How do I edit an XDTO package schema in 1C?▼

Use the unica.xdto.edit MCP tool with a logical metadata path like XDTOPackage.<Name> and an operation such as add-property or add-object-type. Always run the request with dryRun: true first, then repeat the identical request with dryRun: false only after user confirmation.

How to add a property to an EnterpriseData type in 1C?▼

Call unica.xdto.edit with operation add-property, the target typeName, and a property object containing name, type, and minOccurs. For nested anonymous types, pass propertyPath, for example СсылкаНаОбъект inside ЛюбаяСсылка.

What operations does unica.xdto.edit support?▼

Version 1 supports add-value-type, add-object-type, add-property, remove-type, and remove-property. Each call performs exactly one operation and publishes at most one atomic mutation; multi-step changes run as an ordered sequence of preview/apply pairs.

Can I pass the Package.bin file path directly to the XDTO tools?▼

No. Never pass paths to XDTOPackages/.../Ext/Package.bin, since that is internal platform dump layout. Always address packages logically via sourceSet and metadataPath in the form XDTOPackage.<Name>.

Why does an XDTO edit get rejected when adding a property with a QName type?▼

The writer rejects edits when the QName prefix has no visible declaration or maps ambiguously to multiple URIs in the package. It only re-declares a prefix locally when exactly one proven prefix-to-URI mapping exists; it never guesses namespace URIs.