form-validate

Validates 1C:Enterprise managed form XML for structural errors and event bindings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managed forms in 1C:Enterprise are defined in Form.xml files where structural mistakes such as duplicate IDs, broken DataPath references, or invalid event handlers only surface at runtime. This Skill checks a form right after creation or modification so errors are caught before deployment. ## Core Features & Use Cases - Structural validation: Checks Form.xml for unique element IDs, companion elements, and correct DataPath and command references. - Event matrix checks: Validates form and element events against the platform matrix, returning stable FORM_EVENT_* codes for duplicates, empty handlers, and wrong contexts. - Extension awareness: When a form has a direct BaseForm, verifies callType values (Before, After, Override) and flags unverifiable bindings with FORM_EVENT_CONTEXT_UNKNOWN. - Use Case: After editing a catalog item form, run validation on the form directory to confirm all event handlers and extension bindings are correct before committing. ## Quick Start Ask the assistant to validate the managed form at Catalogs/Номенклатура/Forms/ФормаЭлемента and report any structural or event errors.

Frequently Asked Questions about form-validate

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

FAQPage Schema
How do I validate a 1C managed form after editing it?▼

Call the unica.form.validate MCP tool with the FormPath pointing to the form directory or the Form.xml file. It checks ID uniqueness, DataPath references, command links, and event handlers, returning stable error codes for each problem found.

What errors does 1C form validation detect?▼

It detects duplicate element IDs, missing companion elements, incorrect DataPath and command references, and event issues such as duplicates, empty handlers, and wrong element or event names. Event problems return stable FORM_EVENT_* codes.

Can I validate a 1C form by logical metadata address instead of file path?▼

Yes, pass sourceSet and metadataPath such as Catalog.<Object>.Form.<Form> instead of FormPath. Exactly one selector is allowed; providing both is rejected with the selector_conflict error code.

Does form validation support 1C extension forms with BaseForm?▼

Yes, when a form has a direct BaseForm the validator checks callType values, allowing only Before, After, or Override. Borrowed forms without a resolvable main attribute get a FORM_EVENT_CONTEXT_UNKNOWN warning for unverifiable bindings.

Why does form validation stop before checking everything?▼

Validation stops after the MaxErrors limit, which defaults to 30. Increase MaxErrors or use the Detailed flag to see all checks including successful ones.