epf-build

To build 1C external data processors and reports from XML source files, you compile the root XML file directly into an EPF or ERF by launching the 1C Designer with deterministic build arguments. The process validates inputs and resolves the 1C platform path automatically.

Yes, you can compile an EPF from XML sources referencing metadata objects without a full database. When an infobase is absent, the build process creates a temporary stub database with metadata placeholders to prevent compilation failures on reference types.

Yes, the 1C EPF build process supports both file-based and server-based infobases. It reads project settings to automatically select the appropriate infobase type before launching the 1C Designer to compile the external data processor or report.

The best way to automate ERF compilation from a repository with XML structure and 1C metadata is to use a build skill that auto-detects the 1C platform, resolves the infobase, and executes Designer with deterministic arguments to generate the final report file.

Building an external 1C report from XML fails on register record sets and metadata references when the target infobase lacks the required schema. Creating a temporary stub database with metadata placeholders resolves these missing dependencies during compilation.

No, you do not need to manually specify the 1C platform path when building external data processors. The build mechanism automatically resolves the platform installation path and selects the appropriate environment based on your project settings.