meta-edit

To safely edit 1C metadata XML, apply precise atomic changes to attributes, tabular sections, and properties. This approach uses deterministic path resolution and whitespace-preserving DOM updates to maintain configuration integrity during refactoring.

Yes, you can batch update 1C catalog and document properties using flexible JSON-defined change sets. This allows you to apply coordinated, multi-step metadata refactoring across multiple configuration objects in one operation.

Yes, modifying registers, enums, and tabular sections in 1C is fully supported. The process normalizes 1C types and enum values while applying safe edits across catalogs, documents, and other metadata objects.

The best way to rename a field in a 1C document during migration is to use atomic metadata changes. This method ensures type normalization and support-state guardrails are applied to prevent configuration corruption.

Yes, you need lxml to process 1C configuration XML files. It provides the underlying XML parsing and whitespace-preserving DOM update capabilities required for deterministic path resolution and safe metadata editing.