---
title: "Directory \"OrganizationsAttachedFiles\" — Technical Description (Accounting for Kazakhstan 3.0.74.2)"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/spravochnik-organizaciiprisoedinennyefayly-tehnicheskoe-o-en
source: BuhGPT
---

# Directory "OrganizationsAttachedFiles" — Technical Description (Accounting for Kazakhstan 3.0.74.2)

> **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name AttachedFilesOrganizations Full Name Catalog.AttachedFilesOrganizations ( Catalogs.AttachedFilesOrganizations ) Synonym “Attached Files (Organizations)” Configuration 1C:Accounting for Kazakhstan, ed. 3.0.74.2 File Own

---

1. Identification

Parameter
Value

Object Type
Catalog

Name
AttachedFilesOrganizations

Full Name
Catalog.AttachedFilesOrganizations (Catalogs.AttachedFilesOrganizations)

Synonym
“Attached Files (Organizations)”

Configuration
1C:Accounting for Kazakhstan, ed. 3.0.74.2

File Owner
CatalogReference.Organizations

Where to Find
Navigation link e1cib/list/Catalog.AttachedFilesOrganizations. In the interface, it does not appear as a standalone object — work is conducted from the organization card via the “Attached Files” command.

Purpose. The catalog is intended for storing files attached to the elements of the “Organizations” catalog (both for the organization itself and for counterparties, if the storage model allows it). This is part of the standard universal subsystem for working with files in BSP (Library of Standard Subsystems). It stores documents, scans, images, and other materials related to a specific organization: copies of certificates, charter documents, scans of contracts, images of seals/logos, etc.

Files can be stored in two ways:

- in the information base — in a property of type ValueStorage;

- in file storage volumes — in external file storage on disk/network resource (then the FilePath property is filled).

Supported: file versioning, electronic signature (ES), encryption, text extraction for full-text search. Access to the file is strictly regulated by the rights to the owning organization: if the user does not have read access to the organization, they will not see the files attached to it.

2. Attributes and Table Parts

2.1 Header Attributes

Name
Type
Mandatory
Purpose

Author
CatalogReference.Users
ShowError
The user who uploaded the file. Automatically filled upon creation; mandatory for tracking the history of changes.

FileOwner
CatalogReference.Organizations
DontCheck
The organization to which the file is attached. Determines access rights: the file is visible only if access to the organization is granted.

UniversalModificationDate
DateTime
DontCheck
Date/time of the last modification of the file in UTC. Used for synchronization and tracking the relevance of versions.

CreationDate
DateTime
ShowError
Date/time of the file upload to the database. Mandatory, automatically filled upon the first save.

Encrypted
Boolean
DontCheck
Encryption flag. If True, the file is accessible only to users with the corresponding decryption certificates.

ModifiedBy
CatalogReference.Users
DontCheck
The user who last modified the file or its properties. Automatically updated upon each save.

ImageIndex
Number
DontCheck
Index of the file type icon (by extension) for display in lists.

Description
String
DontCheck
User text description of the content/purpose of the file.

SignedByES
Boolean
DontCheck
Flag indicating the presence of an electronic signature. True — certificates and signatures are attached to the file.

FilePath
String
DontCheck
Full path to the file when stored in the volume. Automatically filled if FileStorageType = “In the volume on disk”.

Size
Number
DontCheck
File size in bytes. For monitoring disk space and upload size limits.

Extension
String
DontCheck
File extension (pdf, docx, jpg, etc.). Determines the type and ability to view/edit.

EditingUser
CatalogReference.Users
DontCheck
The user who has taken the file for editing (lock). While filled — others cannot edit.

Standard attributes of the file subsystem (present in objects of this type in BSP, complementing the list above):

Name
Type
Purpose

FileStorageType
Enumeration.FileStorageTypes (String)
Method of storage: in the information base / in the volume on disk.

FileStorage
ValueStorage
Binary data of the file when stored in the IB.

StorageVolume
CatalogReference.FileStorageVolumes
The volume in which the file is located (when stored on disk).

VersionOccupied / CurrentVersion
CatalogReference.…FileVersions
Reference to the current version of the file in the versioning mechanism.

TextStorage
ValueStorage
Extracted text of the file for full-text search.

SignedByES / Encrypted
Boolean
Service flags of the state of crypto operations (see above).

The attribute Name (standard attribute of the catalog) stores the file name without the extension.

2.2 Table Parts

For the service catalog of attached files, there are generally no own table parts. Multiple data (versions, signatures, encryption certificates) are stored in separate subordinate catalogs/registers of the subsystem (for example, …FileVersions) and in storage attributes, not in the table parts of the main element.

3. Forms

Form
Purpose

ElementForm
File card: name, description, author, dates, ES/encryption flags, open/save/edit commands.

ListForm
List of attached files, usually embedded in the organization card (panel “Attached Files”).

SelectForm
Selecting a file from the list in other forms.

The main working scenario is not the direct opening of catalog forms, but the embedded form of attached files in the organization card (standard form of the “File Management” subsystem in BSP), from which commands for adding, viewing, editing, signing, and encrypting are called.

4. Key Module Procedures

No separate BSL code for this object is attached in evidence. The logic is standard for attached files in BSP; it is mainly implemented in the common modules of the subsystem, not in the module of the catalog itself.

Object Module (BeforeWriting, OnCopying):

- filling Author, CreationDate upon creation; updating ModifiedBy, UniversalModificationDate upon writing;

- controlling file occupancy (EditingUser) before changing data.

Common modules of the file management subsystem (standard call points):

- FileManagement / FileManagementService — adding a file, reading/writing FileStorage, transferring between storages (IB ↔ volume);

- mechanism “Occupy/Release” — setting and removing editing lock through the EditingUser property;

- versioning — creating a new version when saving a modified file, maintaining history;

- ES and encryption — setting/checking signatures (SignedByES), encryption/decryption (Encrypted) using the “Electronic Signature” subsystem;

- text extraction — background filling of TextStorage for full-text search.

5. Posting and Movements

The catalog is not a document and does not perform posting — it does not generate movements in accounting/accumulation registers and accounting entries. This is a service data storage object.

Indirectly related to the recording of the element are:

- recording binary data in the FileStorage property (when stored in the IB) or placing the file in the volume with filling FilePath (when stored on disk);

- registration of the version in the file versioning mechanism;

- text indexing for full-text search.

For comparison: real postings in the configuration generate accounting documents (sales, receipts, etc.). For example, the sale of goods in the RK gives Dr 1210 Cr 6010 (income), Dr 7010 Cr 1330 (cost), Dr 1210 Cr 3130 (VAT at the rate of 16%, ed. 2026). The attached files catalog has no relation to this — it merely stores documents attached to the organization (for example, a scan of the VAT registration certificate).

6. Related Objects and Input Based On

Relation
Object

Owner
Catalog.Organizations — the element to which the file is attached.

Author / ModifiedBy / EditingUser
Catalog.Users.

Storage on Disk
Catalog.FileStorageVolumes.

Versions
Subordinate catalog of file versions in the subsystem.

ES/encryption
Subsystem “Electronic Signature” (certificates, signatures).

Full-text Search
Index by TextStorage.

Input based on is not applicable for the service catalog. The creation of an element is performed by the command to add a file from the organization card (drag and drop, selection from disk, from email/scanner).

7. Extension Points

- Configuration Extension — adding attributes (for example, category/type of document, validity period) and commands in forms without removing from support; overriding handlers BeforeWriting.

- Additional Attributes and Information — through the properties subsystem of BSP, files can be classified (document type, responsible) without changing metadata.

- Programming Interfaces of the “File Management” Subsystem — export methods of common modules for programmatically adding/reading files, working with versions, ES, and encryption.

- Storage Volume Configuration — moving files from IB to volumes to reduce database size; switching FileStorageType.

- Access Restriction (RLS) — access is inherited from the rights to the owning organization; if necessary, specified in access restriction templates.

- BSP Event Handlers (FileManagementOverridable and analogs) — points for embedding custom logic when working with attached files.

Requires verification (version-specific): the exact composition of the subsystem attributes (FileStorageType, StorageVolume, TextStorage) and names of common modules may differ in the specific build 3.0.74.2 — please check with the configurator.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_