--- title: "Processing \"DataExportImportUserSettingsExportManager" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-24 canonical: https://buhgpt.kz/suraqtar/obrabotka-vygruzkazagruzkadannyhmenedzhervygruzkinastroek-en source: BuhGPT --- # Processing "DataExportImportUserSettingsExportManager > **TL;DR:** 1. Identification Parameter Value Object type Data processor (DataProcessor) Name ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиНастроекПользователей Full name DataProcessors.ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиНастроекПользователей Synonym "Data export import user settings export m --- 1. Identification Parameter Value Object type Data processor (DataProcessor) Name ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиНастроекПользователей Full name DataProcessors.ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиНастроекПользователей Synonym "Data export import user settings export manager" Configuration Trade Management for Kazakhstan, 3.4.5.21 Subsystem Technological — data exchange/transfer, user administration Where to find e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиНастроекПользователей Purpose. This is a service (technological) data processor at the library level, part of the "Data Export/Import" mechanism. It is responsible for transferring user settings — saved form settings, report variants, layouts, personal session parameter values, and settings storages — when exporting an infobase to a file (export archive) and subsequently importing it into another base. The data processor is not an accounting object: it does not participate in goods movement, pricing, tax calculation, or generation of e-invoices/e-waybills. Its task is to preserve the user's "desktop" (individual interface settings) during base migration, upgrade, database compaction, or creation of a test environment. Important. As a technological data processor, it has no posting, register movements, or accounting entries. The "Posting" and "Basis for entry" sections below are discussed in this context, rather than through the chart of accounts of Kazakhstan. 2. Attributes and tabular sections Data processors of this type in the configuration generally do not have declared attributes and tabular sections at the metadata level — the entire data structure is described programmatically in the object module and on the forms. Typical set of working data operated by the manager: Form parameters/fields (form attributes, not object attributes): Field Purpose ВыгружатьНастройкиПользователей Flag to include transfer of user settings in the overall export package СписокПользователей (tabular section/form tree) List of infobase users with selection flags; determines whose settings are exported/imported ХранилищаНастроек Set of system storages: form settings, report variants, user report settings, form data settings, common settings РежимЗагрузки Application method on import: replace existing settings / add missing only / skip СопоставлениеПользователей Table matching "source user → destination user" (by name/ID) for correct transfer when the user composition differs Tabular sections (working, generated programmatically): Tabular section Columns (typical) Purpose Users User, Identifier, Export Selection of users for the operation Settings SettingType, ObjectKey, SettingKey, Presentation List of settings storage items to be exported 3. Forms Form Purpose Data processor form (main) Process management: selecting users, selecting the composition of settings storages, launching export/import, displaying progress and result Export settings form (if available) Detailed configuration of the composition of transferred settings and the application mode on the destination User mapping form (if available) Manual mapping of source and destination users before import In the standard delivery, the data processor is more often called not directly, but as part of the overall data export/import scenario, so its own form may be used in debugging/administrative mode. 4. Key module procedures No direct BSL evidence for this object was provided (only the "purpose" facet is present in the source), so below is the typical contract for manager data processors that export settings of this kind. Specific procedure names require verification against the object module of the installed 3.4.5.21 build. Object module (general contract): - ПодготовитьДанныеВыгрузки(Параметры) — forms the composition of settings to be transferred: iterates through the storages ХранилищаНастроек.СистемныеНастройки, ХранилищаНастроек.НастройкиОтчётов, ХранилищаНастроек.НастройкиФорм, ХранилищаНастроек.НастройкиДанныхФорм and collects keys for the selected users. - ВыгрузитьНастройкиПользователей(Пользователи, Приёмник) — reads values from the storages (ХранилищеНастроек.Загрузить) and serializes them into the export package structure. - ЗагрузитьНастройкиПользователей(Источник, РежимЗагрузки, Сопоставление) — restores settings in the destination (ХранилищеНастроек.Сохранить) taking into account user mapping and the selected replace/add mode. - СопоставитьПользователей(ПользователиИсточника, ПользователиПриёмника) — builds a match by name/identifier, flags unmatched entries. Form module (typical handlers): - ПриСозданииНаСервере — initializes the user list and the composition of storages. - ВыгрузитьНажатие / ЗагрузитьНажатие — starts the operation, usually as a background job with progress indication. - ОбработатьРезультатФоновогоЗадания — outputs a log: how many settings and for which users were transferred, list of skipped items. 5. Posting and movements The data processor is not posted and does not generate movements in accumulation/information registers or accounting entries. It modifies system platform settings storages, not accounting data. For context on the Kazakhstan configuration (these accounts and rates relate to accounting documents, not to this data processor): typical Kazakhstan chart of accounts — 1210 (short-term accounts receivable from customers), 1030 (cash in current accounts), 1330 (inventory), 3310 (accounts payable to suppliers), 3130 (VAT payable), 6010 (revenue from sales), 7010 (cost of sales); 2026 VAT rate — 16%. This data processor does not affect any of these accounts. 6. Related objects and basis for entry - Basis for entry is not applicable for a service data processor. - Related objects: the "Data Export/Import" mechanism (companion data processors of the same family), the Users catalog and InfobaseUsers, system settings storages (СистемныеНастройки, НастройкиОтчётов, НастройкиФорм, НастройкиДанныхФорм, ХранилищеВариантовОтчётов), as well as the SSL "Users"/"User Settings" subsystem. - The data processor is invoked by full infobase export scenarios, database compaction, migration, and preparation of test bases. 7. Extension points - Configuration extension: a form handler can be added (&After("ПриСозданииНаСервере")) to preset the composition of storages or restrict the user list by security policy. - Composition filtering: overriding data preparation to exclude sensitive personal settings when exporting to an external environment. - User mapping: customizing the СопоставитьПользователей rule for a proprietary identification scheme (e.g., by e-mail or external AD code). - Logging: connecting operation log recording to the event log via the subsystem's common module. - Scheduled use: wrapping the manager call in a scheduled/background job for automated settings transfer in conjunction with a database update. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_