form-decompile

To convert a 1C Form.xml file into JSON, you decompile the managed form into a compact JSON draft. This allows you to inspect and structurally refactor element trees, requisites, and commands without traversing the raw XML.

Yes, you can use JSON drafts to scaffold and clone 1C managed forms. Decompiling an existing form into a JSON draft provides a safer workflow for adapting it into a new form by reorganizing element trees and attributes before compiling it back.

When decompiling unsupported 1C form constructs, the decompilation process uses validation-aware behavior to detect risky constructs. It falls back or stops instead of silently corrupting the resulting JSON draft.

Yes, 1C form decompilation handles grouping and list settings. It targets common layout and appearance scenarios across managed 1C forms, extracting element trees, requisites, commands, and list settings into a structured JSON format.

The best way to structurally refactor 1C managed forms is by decompiling the Form.xml into a compact JSON draft. This structure-first approach lets you reorganize element trees, attributes, and commands efficiently for larger form changes.