1C Form Compile — Generate Form.xml from JSON DSL

Takes a compact JSON definition (20–50 lines) and generates a complete, valid Form.xml (100–500+ lines) with namespace declarations, auto-generated companion elements, and sequential IDs.

When designing a form from scratch (5+ elements or unclear requirements) — load the 1c-form-patterns skill first for archetypes, naming conventions, and advanced patterns. For simple forms (1–3 fields with clear requirements) — not needed.

Usage

1c-form-compile <JsonPath> <OutputPath>

Command

powershell.exe -NoProfile -File skills/1c-form-compile/scripts/form-compile.ps1 -JsonPath "<json>" -OutputPath "<xml>"

JSON DSL Reference

Top-Level Structure

{
  "title": "Form Title",
  "properties": { "autoTitle": false, ... },
  "events": { "OnCreateAtServer": "OnCreateAtServerHandler" },
  "excludedCommands": ["Reread"],
  "elements": [ ... ],
  "attributes": [ ... ],
  "commands": [ ... ],
  "parameters": [ ... ]
}

• •title — form title (multilingual). Can also be in properties, but top-level is preferred
• •properties — form properties: autoTitle, windowOpeningMode, commandBarLocation, saveDataInSettings, width, height, etc.
• •events — form event handlers (key: 1C event name, value: procedure name)
• •excludedCommands — excluded standard commands

Elements (key determines type)

Common Properties (all element types)

Allowed Event Names (on)

The compiler warns about unknown events. Names are case-sensitive — use exactly as shown.

Form (events): OnCreateAtServer, OnOpen, BeforeClose, OnClose, NotificationProcessing, ChoiceProcessing, OnReadAtServer, BeforeWriteAtServer, OnWriteAtServer, AfterWriteAtServer, BeforeWrite, AfterWrite, FillCheckProcessingAtServer, BeforeLoadDataFromSettingsAtServer, OnLoadDataFromSettingsAtServer, ExternalEvent, Opening

input / picField: OnChange, StartChoice, ChoiceProcessing, AutoComplete, TextEditEnd, Clearing, Creating, EditTextChange

check: OnChange

table: OnStartEdit, OnEditEnd, OnChange, Selection, ValueChoice, BeforeAddRow, BeforeDeleteRow, AfterDeleteRow, BeforeRowChange, BeforeEditEnd, OnActivateRow, OnActivateCell, Drag, DragStart, DragCheck, DragEnd

label / picture: Click, URLProcessing

labelField: OnChange, StartChoice, ChoiceProcessing, Click, URLProcessing, Clearing

button: Click

pages: OnCurrentPageChange

Input Field

Checkbox

Label Decoration

Group

Value of the key sets orientation: "horizontal", "vertical", "alwaysHorizontal", "alwaysVertical", "collapsible".

Table

Important: a table requires an associated form attribute of type ValueTable with columns (see "Bindings" section).

Pages (pages + page)

Button

Command Bar (cmdBar)

Popup Menu

Used inside cmdBar to group buttons:

{ "cmdBar": "Panel", "children": [
  { "popup": "Add", "title": "Add", "children": [
    { "button": "AddRow", "stdCommand": "Items.Add" },
    { "button": "AddFromDocument", "command": "AddFromDocument", "title": "From Document" }
  ]}
]}

Attributes

{ "name": "Object", "type": "DataProcessorObject.Import", "main": true }
{ "name": "Total", "type": "decimal(15,2)" }
{ "name": "Table", "type": "ValueTable", "columns": [
    { "name": "Product", "type": "CatalogRef.Products" },
    { "name": "Quantity", "type": "decimal(10,3)" }
]}

• •savedData: true — saved data

Commands

{ "name": "Import", "action": "ImportHandler", "shortcut": "Ctrl+Enter" }

• •title — title (if different from name)
• •picture — command picture

Type System

Bindings: Element + Attribute

Tables and some fields require an associated attribute. Elements reference attributes via path.

Table — table element + ValueTable attribute:

{
  "elements": [
    { "table": "Items", "path": "Object.Items", "columns": [
      { "input": "Product", "path": "Object.Items.Product" }
    ]}
  ],
  "attributes": [
    { "name": "Object", "type": "DataProcessorObject.Import", "main": true,
      "columns": [
        { "name": "Items", "type": "ValueTable", "columns": [
          { "name": "Product", "type": "CatalogRef.Products" }
        ]}
      ]
    }
  ]
}

Or, if table is bound to a form attribute (not Object):

{
  "elements": [
    { "table": "DataTable", "path": "DataTable", "columns": [
      { "input": "Name", "path": "DataTable.Name" }
    ]}
  ],
  "attributes": [
    { "name": "DataTable", "type": "ValueTable", "columns": [
      { "name": "Name", "type": "string(150)" }
    ]}
  ]
}

Auto-generation

• •Companion elements: ContextMenu, ExtendedTooltip, etc. are created automatically
• •Event handlers: "on": ["OnChange"] → auto-named handler
• •Namespace: all 17 namespace declarations
• •IDs: sequential numbering, AutoCommandBar = id="-1"
• •Unknown keys: warning about unrecognized keys

Verification

1c-form-validate <OutputPath>    — check XML correctness
1c-form-info <OutputPath>        — visual structure summary

Notes for External Data Processors (EPF)

• •Main attribute type: ExternalDataProcessorObject.ProcessorName (not DataProcessorObject)
• •DataPath: use form attributes (AttributeName), not Object.AttributeName — external data processors have no object attributes in metadata
• •Reference types: CatalogRef.XXX, DocumentRef.XXX, etc. may not build in an empty infobase — use string or basic types for standalone builds

MCP Integration

Use search_metadata MCP tool to verify metadata types when defining attributes. Use templatesearch to find similar form patterns.