inspect

Inspecting a 1C XML metadata export provides a compact, human-readable analysis of configuration, managed forms, DCS templates, and role rights. You can load the correct XML file from a given path and use mode-based verbosity to balance speed and completeness.

Yes, you can drill down into specific elements within a 1C XML file using an optional name parameter. This allows targeted inspection of particular metadata objects, subsystem nodes, tabular sections, or role rights details without analyzing the entire export.

Reading large 1C XML configuration files safely involves using a safety-first inspection workflow that outputs paginated UTF-8 text. This approach explicitly avoids modification or compile logic, ensuring the original metadata remains untouched while providing a structured overview.

Yes, 1C XML inspection supports analyzing MXL spreadsheet layouts and subsystems. It provides a unified view of configuration metadata, managed forms, DCS templates, and role rights in one place, allowing comprehensive structural analysis before making changes.

Validating configuration compatibility before editing a 1C XML object requires inspecting the metadata structure to locate the exact element to modify. By using overview, brief, or full modes, you can understand the structure and validate compatibility as a pre-change workflow step.