Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
You installed or updated a configuration extension (for example, a customization from a contractor or an additional printable form), and afterwards, when opening a document, something popped up like "Extension object not found" or "Object identifier is out of date." Or the technical support told you: "go to the ExtensionObjectIDs directory and check whether there are objects marked for deletion." You open the list — and there are incomprehensible rows like Catalog.AdditionalAttributes without amounts, accounts, or a "Post" button. This is normal. You have landed in a service directory of the platform, not in an accounting document.
The main thing right away, so as not to waste time: this is a technical directory. It has no postings, no printable forms, no ESF or SNT, and there is no need to fill it in manually. Below is what it is, where it comes from, and what to do with it.
1. Purpose
The directory stores "anchors" (permanent references) to metadata objects that came into the database from configuration extensions. It is needed so that program code can reliably reference an extension object even after that extension is renamed or reinstalled. This is part of the "Standard Subsystems Library" (SSL) mechanism, an analog of the MetadataObjectIDs directory, only for extensions.
2. Where to find it
In the regular accountant's interface there is no menu item for it — and that's correct. You can open it in two ways:
Via a navigation link. Main menu (the arrow button in the top left corner or "Tools") → Functions for a technical specialist (it must first be enabled in "Settings → Options → Display the "All functions" command"), or directly: Main menu → File → no… the easiest way is to paste a link. Copy:
e1cib/list/Справочник.ИдентификаторыОбъектовРасширенийand paste it via Tools → Show navigation link → Go to navigation link (or the shortcut that opens the navigation line).
Via "All functions". Main menu → All functions → expand the Catalogs branch → find ExtensionObjectIDs.
If there is no "All functions" item — enable it: Tools → Options → "Display the "All functions" command".
2a. How to find out your release
Main menu → Help → About the program (or "Program information"). In the window that opens you will see:
- the platform version (for example, 8.3.24.x);
- the configuration release — the line "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)".
This entire instruction refers to release 3.0.74.2. If yours is different — the set of service attributes may differ.
3. How to fill it in
The correct answer is: no way — it is not filled in manually. The directory is maintained programmatically, upon connecting, updating, and deleting extensions. The "Create" button here has no practical meaning for you: if you create a row manually, you will get a "dangling" identifier that is not linked to any real object, and this is more likely to cause harm.
Nevertheless, you will see the fields — let's go over what each of them means and what happens if it is "wrong".
| Field | What it means | What happens if the value is incorrect |
|---|---|---|
| Full name (key) | The full name of the extension metadata object, for example Catalog.AdditionalAttributes or DataProcessor.BankImport. The code uses it to find the object. |
If the full name does not correspond to any object in the current set of extensions — the identifier is considered "out of date", the object stops being found, and documents/data processors based on it produce an error. |
| Description | The synonym of the object (the way it is named in the Designer). Serves for human reading. | Does not affect operation directly, but you use it to orient yourself as to "what this row is". |
| Code | The internal code of the record. Assigned automatically. | If you change it — you risk breaking references. Don't touch it. |
| Deletion mark | A standard indicator: the extension object has been deleted/disabled. | If the mark is set but the object is actually needed — some functions will not work. You cannot remove the mark manually; it is removed by the standard identifier update mechanism. |
Separately I'll note: the directory may contain attributes such as a "deleted object" indicator and a service reference to a new item (used when transferring identifiers). The exact composition of these hidden attributes is version-specific and requires verification in a specific release via the Designer — they do not affect the accountant's work.
4. Worked example
There are never any postings and amounts here, so a "Dr/Cr example" for this object would be a fabrication — giving it would be dishonest. Instead — a realistic scenario, the very one you came here for.
Situation. A contractor sent an extension PrintableFormsExtension.cfe, which adds a printable form "Reconciliation report (extended)" to the "Sales" document. You connected it: Master data and administration → Printable forms, reports and data processors → Extensions → Add from file.
What happens inside. Upon connection, the SSL mechanism registers the extension objects. In the ExtensionObjectIDs directory, for example, a row appears:
- Full name:
DataProcessor.ReconciliationReportExtended - Description: "Reconciliation report (extended)"
- Code: assigned automatically
- Deletion mark: not set
Now the printable form's code addresses the data processor not by name directly, but through this identifier. You deleted the extension and installed a new version — the object name is the same, the identifier is reused, and the printable form continues to open. If the identifier did not exist, you would have to reconfigure the bindings on every reinstallation.
If something went wrong. The contractor renamed the data processor in the new version to DataProcessor.ReconciliationReport2. The old row DataProcessor.ReconciliationReportExtended remains with a deletion mark, and a new one appears. The print button "hardwired" to the old identifier stops working. It is fixed by updating the extension to the agreed version or by reinstalling — nothing is edited manually in the directory.
5. Operation types
There are none. This is a directory, not a document: it has no "Operation type", no posting, no statuses. There are only items (records about extension objects) and standard platform actions: open, find, set/remove the deletion mark (not recommended).
6. What is generated upon posting
The directory is not posted, therefore:
- Postings (account movements) — none.
- Movements in accounting/accumulation registers — none.
- Electronic documents (ESF in the ESF IS, SNT) — none. These documents are generated by "Sales", "Acquisition", "Invoice (issued)", etc., but not by service directories.
The only "movement" is a technical one: upon connecting/updating an extension, the rows of this directory are created, updated, or marked for deletion automatically.
7. Printable forms
The directory has no printable forms. Neither a contract, nor a report, nor an invoice is printed from here. If you need a printable form — you look for it at the corresponding sales/acquisition document, and this directory merely helps such a printable form from an extension "find itself".
8. Common mistakes
"Extension object not found" / "Extension object identifier is out of date". Usually after reinstalling an extension of a different version. Solution: Master data and administration → Printable forms, reports and data processors → Extensions — check that the required extension is connected and active; if necessary, delete it and install the agreed version. After the update, the identifiers are rebuilt in the standard manner.
"Failed to complete the scheduled job for updating object identifiers". Occurs when the update was running with active users or was interrupted. Solution: have all users end their work, log back in as administrator, and let the SSL mechanism finish the update (usually performed on the first launch after the update).
Duplicate rows with the same "Full name", one of them — with a deletion mark. This is not an error: the old record is marked, and a new one is created. There is no need to remove/set marks manually — you will break the bindings.
"Access rights violation" when trying to open the directory. Your user does not have administrative rights. This is normal: an ordinary accountant does not need access here. Contact the administrator.
9. FAQ
What kind of directory is this at all and why do I have it? A service directory of the 1C platform (part of the SSL). It stores permanent identifiers of objects that came from configuration extensions, so that the code references them reliably. It appears automatically as soon as extensions are used in the database.
Can I clean it up or delete records? No. Deleting rows breaks references to extension objects and breaks the related functions (printable forms, data processors, additional attributes). Manage the extensions themselves, not the directory.
Does it affect VAT, IIT, taxes, and reporting? No. It is a technical entity. It does not affect the calculation of VAT (in the RK, from 2026, the rate is 16%), IIT, MPC, social tax, or the generation of ESF/SNT in any way.
Why is there no "Post" and "Print" button? Because it is a directory, not a document. Postings and printable forms are provided by sales, acquisition, cash documents, etc.
After a configuration update, new rows appeared in it — is this normal? Yes. During an update and when connecting extensions, the mechanism adds/updates identifiers. Nothing needs to be done.
I have a row with a deletion mark, but the function is needed. What should I do? Do not remove the mark manually. Reinstall the required version of the extension — the identifier will be restored in the standard manner, or agree on the version with the contractor.
How does it differ from "MetadataObjectIDs"?
MetadataObjectIDs stores anchors to objects of the configuration itself, while ExtensionObjectIDs stores them to objects that came from extensions. The mechanism is the same, the scope of application is different.
Do I even need to go in there at all? In normal work — no. It is accessed by the administrator or the contractor when diagnosing problems with extensions. If you were not asked to — close it and continue working.
Can this directory "bloat" the database? Practically no: the records are small and there are few of them (by the number of objects in the extensions). The database size is affected by documents and registers, not by it.
10. Related documents
- On the basis of what it appears: records are created by the SSL mechanism upon connecting/updating/deleting configuration extensions (
Master data and administration → Printable forms, reports and data processors → Extensions) and additional reports and data processors. - What it is related to in meaning: the
MetadataObjectIDsdirectory (an analog for the main configuration), the infobase version update subsystem, the "Additional reports and data processors" mechanism. - What is entered "on the basis" of it: nothing. A service directory has no "entry on the basis".
How to find out your release
Main menu → Help → About the program. There you will find the "1C:Enterprise" platform version and the configuration release. Compare with the caption below — if the release differs, the composition of the directory's service attributes may have changed.
The material was prepared for "1C:Accounting for Kazakhstan", edition 3.0, release 3.0.74.2.