Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
To be honest, without pretense. "FullPathsToForms" is not an accounting document. There are no amounts, no VAT, no entries, no electronic invoices (ESF), and no printed forms. This is an internal service reference guide of the configuration. It stores textual addresses of forms (for example, Document.SaleOfGoodsServices.Form.FormDocument) so that other mechanisms of the program can refer to a specific form not by a string in the code, but by an element of the reference.
Therefore, the methodology will be different. I will not invent an example with entries Dr 1210 Cr 6010 — they do not physically exist here. Instead, I will analyze in what real situation an accountant encounters this, what the fields mean, and what will happen if you try to edit them.
Real situation in which you open this
A support specialist calls you (or you read an article on the forum) and says: "Open the reference FullPathsToForms and check if there is an entry for the form of such-and-such document." Or you are setting up additional processing / external printed form and in the wizard see the option "full path to the form." Or after updating the configuration, an error appeared in the registration log with the words "full path to the form not found."
In all these cases, you are not "keeping records." You are looking under the hood. And the main rule here is one: you can look, but do not clean or delete with your hands.
1. Purpose
The reference stores full paths (addresses) to configuration forms in the form of strings. These records are referenced by service mechanisms: connecting external/additional processing and printed forms, setting up form openings, as well as mechanisms of standard subsystems (BSP), which need to identify the form unambiguously by the reference element, not by a "raw" string.
2. Where to find
In the typical accountant interface, this reference is not in the section menu — it is service and intentionally hidden. You can open it in two ways:
- Main menu → Functions for technical specialist (the "All functions" mode must be enabled in settings) → section "References" → "FullPathsToForms".
- Direct navigation link (the most reliable way). Copy the line below, then: Main menu → Service → "Go to navigation link" and paste it:
e1cib/list/Reference.FullPathsToForms
If the "All functions" item is not available, enable it: Service → Parameters → "Show the command 'All functions'" (in thick/managed mode — the corresponding checkbox in settings).
2a. How to find out your release
Main menu (icon with a circle "i" or "Help") → "About the program". In the opened window, you will see:
- platform version (for example, 1C:Enterprise 8.3.x.xxxx);
- configuration version — it should say "Accounting for Kazakhstan", version 3.0, release 3.0.74.2.
The release is important: the set of service paths to forms changes from release to release along with the configuration forms. The instructions below describe the behavior specifically for 3.0.74.2.
3. How to "fill in" (and why usually — you don't need to)
Records in this reference are added automatically by the configuration mechanisms: when the program first needs a reference to a form, it creates (or finds) the necessary element itself. Manual creation is justified only in narrow support scenarios. The fields are simple:
| Field | Purpose | What happens if entered incorrectly |
|---|---|---|
| Code (MANDATORY) | Internal identifier of the element. Assigned automatically. | Duplicate codes break the links of mechanisms that search for the record by code. Do not change manually. |
| Name / Representation | Human-readable name of the record, by which you recognize it in the list. | The error is not critical for operation, but you will not find the necessary line later. |
| Full path to the form (MANDATORY, key) | The actual address of the form in the format View.Name.Form.FormName, for example Document.InvoiceIssued.Form.FormDocument. The mechanism opens the necessary form by it. |
Typo or non-existent path → the form does not open, the processing "does not see" the form, an error appears in the registration log regarding path search. |
Practical recommendation: if you really need to add a path (for example, for an external printed form), copy the exact name of the form from the configurator or from the documentation for the processing, rather than typing it manually. Any extra space or incorrect case — and the path will not work.
4. Analyzed example
There are no numerical examples with money here, so I will analyze a typical service scenario — connecting an external printed form "Invoice" to the document "Invoice to Customer".
- You receive a file of the external printed form (
.epf) from the developer and connect it: Administration → Printed forms, reports and processing → Additional reports and processing → Create. - In the binding wizard, specify to which object the form relates. At this step, the configuration refers to the reference "FullPathsToForms" to match the processing with the document form
Document.InvoiceToCustomer.Form.FormDocument. - If such a record did not exist yet — the program creates it itself. You will see this: by opening the reference via the link
e1cib/list/Reference.FullPathsToForms, you will find a new line with this path. - Result: printing appears in the "Print" list of the document. No entries, no movements in the registers are created during this process — the reference only "linked" the processing with the form.
Conclusion from the example: the reference element is a technical "bookmark" for the form, not a business operation.
5. Types of operations
The reference has no types of operations in the accounting sense (it is not a document). There are only standard actions with reference elements: create, copy, modify, mark for deletion, find duplicates. There are no "receipt / sale / return" operations here by definition.
6. What is formed "upon processing"
Nothing. The reference element is not processed — references in 1C do not have processing. Accordingly:
- No entries (accounting records) — none.
- No movements in the registers — none.
- No electronic documents (ESF in the ESF IS, VAT) — none.
- No tax consequences (VAT 16%, PIT, WPP, SO, social tax) — none.
All of this is formed by real documents (sale, receipt, invoice). This reference only helps to open their forms. If you need entries and ESF — you opened the wrong object: you need to go to the documents in the "Sales" or "Purchases" section.
7. Printed forms
The reference has no printed forms. A paradox, but true: it itself serves the printing mechanism of other objects, and there is no point in printing a "list of paths to forms." The only thing you can get is standard output of the list (button "More → Output list") for service analysis or sending to support.
8. Common errors
- "Form with the specified full path not found" — the path in the record points to a form that no longer exists in the current release (a common story after an update). How to fix: do not delete the record blindly. Check the current name of the form; if the record referred to external processing — rebind the processing again through "Additional reports and processing," the configuration will correct the path itself.
- "Value is not an object type value" / reference to a non-existent element — the mechanism referred to a reference element that you manually marked for deletion and deleted. How to fix: restore from a backup or reconnect the processing/mechanism so that the record is created again.
- Duplicate records for the same path — appear after manual experiments. How to fix: More → Search and delete duplicates, keep the element that already has references.
- "Insufficient rights" when opening the reference — your profile does not have service rights. How to fix: ask the administrator; a regular accountant usually does not need access here.
9. FAQ
(see a separate FAQ block — questions and answers match this section)
10. Related objects
- Based on what it appears: records are created by configuration mechanisms — primarily when connecting additional reports and processing / external printed forms (section "Administration"), as well as by service subsystems when opening forms.
- What "is entered based on": nothing. Economic documents are not created from this reference. It is auxiliary: it is referred to, but not based on when entering accounting documents.
How to find out your release
Main menu → "About the program" — there you will find the version of the 1C:Enterprise platform and the release of the configuration. If you do not have 3.0.74.2, the set of service paths and the behavior of printing/processing mechanisms may differ; refer to the description of your release.
The instruction is prepared for "Accounting for Kazakhstan," version 3.0, release 3.0.74.2.