--- title: "Processing \"UploadDownloadDataFoldingUserReferencesInSplitData\" in UT for Kazakhstan 3.4" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-24 canonical: https://buhgpt.kz/suraqtar/obrabotka-vygruzkazagruzkadannyhsvertkassyloknapolzovatel-en source: BuhGPT --- # Processing "UploadDownloadDataFoldingUserReferencesInSplitData" in UT for Kazakhstan 3.4 > **TL;DR:** Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). You are transferring a client's database from the cloud (1C:Fresh / rented service) to a boxed version on your own server. The data area upload went through, you loaded it — and suddenly in all docum --- Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). You are transferring a client's database from the cloud (1C:Fresh / rented service) to a boxed version on your own server. The data area upload went through, you loaded it — and suddenly in all documents "Responsible", "Author", "Modified by" became empty or refer to the wrong people. Or vice versa: during the upload a line about "collapsing user references" flashed in the registration log, and you want to understand what it was and whether it broke the data. This is what the processing in question is about. Right away, the main point: this is not an accountant's document. There are no amounts, invoices, or postings here — this is a service tool of the data separation technology. Below is what it does, when it triggers, and what to do with it (and more often — what NOT to do). 1. Purpose The processing serves the data separation mechanism (service model, 1C:Fresh). When uploading and loading a data area, it "collapses" references to users: in separated data (documents, area catalogs) references to users are stored, while the users themselves reside in shared, unseparated data. When transferring the area between information bases, the internal user identifiers do not match — the processing replaces direct references with a neutral representation so that after loading they can be correctly matched. 2. Where to find it The processing is a service tool and is called automatically by the platform and the service technology subsystem during upload/loading of the data area. In the standard Trade Management for Kazakhstan interface there is no menu item for it. To open it directly (for diagnostics, with administrator rights): - Main menu → "All functions" → Processing → find it by name in the list. If there is no "All functions" item: "Service" → "Options…" → enable "Display the 'All functions' command". - Or via a navigation link: Main menu → "File" → "Open by navigation link" and paste: e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхСверткаСсылокНаПользователейВРазделенныхДанных In practice you "see" it not as a form, but as a stage within standard service operations: Administration → Maintenance and the data area upload tools in the service model. 2a. How to find out your release "Help" → "About the program" (or the i icon in the top right corner). In the window that opens — the platform version (e.g., 8.3.2x) and the configuration release "Trade Management for Kazakhstan" (you should have 3.4.5.21). Reference this number when checking the instructions: the behavior of service mechanisms depends on the version of the Standard Subsystems Library included in the release. 3. How to "fill it in" There are no fillable fields in the usual sense here — the processing does not collect data from a form, but works as a method within the upload/load process. It is controlled by transfer operation parameters, not document attributes. What to watch for: Parameter / context Why it is needed What happens with an incorrect value Data area (separator) — REQUIRED Determines whose area is being uploaded/loaded Wrong separator — you will transfer someone else's data or get an empty upload Mode: upload / load — REQUIRED Sets the direction: collapse references (upload) or expand/match (load) Loading into a non-empty area without clearing it — duplication or reference conflicts Upload data file (.xml/archive) — REQUIRED when loading The source from which data and collapsed references are restored Corrupted or partial file — loading will fail with an error User mapping How "neutral" references are bound to recipient users after loading Not mapped — "Responsible/Author" fields will remain empty Rule: this processing is not "posted" manually. It is called by the standard data area upload scenario. Your role is to correctly specify the area, direction, and file in the transfer wizard, and the processing will perform the reference collapsing itself. 4. Worked example Situation. LLP "Astana-Snab" is moving from the 1C:Fresh cloud to a boxed installation. Data area No. 1048. The database has 3 users: Akhmetova (chief accountant), Sidorov (warehouse keeper), Administrator. In the cloud their internal identifiers are one thing, in the boxed database they will be different. What happens during upload: - In the "Sale of Goods and Services" document No. RT-000123 dated 05.09.2026 for the amount of 1,160,000 ₸ (including 16% VAT — 160,000 ₸), the "Responsible" field = Akhmetova. - The processing does not touch the amount, invoices, or VAT. It replaces the direct reference "Responsible → Akhmetova" with a neutral representation (by user name/identifier, not by the internal reference of the source database) and places it in the upload file. What happens when loading into the boxed installation: - The document data is restored as is: amount 1,160,000 ₸, VAT 160,000 ₸ — unchanged. - The processing looks for the user "Akhmetova" in the recipient database and restores the reference. If found — the "Responsible" field again shows Akhmetova. If not found (the user is not set up) — the field will remain unfilled until manual mapping. Postings. These are generated by the sale document itself upon posting, not by this processing. For clarity — here is what the movements of that same RT-000123 look like on the standard chart of accounts of Kazakhstan: Dr Cr Amount, ₸ Description 1210 6010 1,000,000 Revenue from sale (excluding VAT) 1210 3130 160,000 VAT 16% payable 7010 1330 640,000 Cost of goods sold written off Conclusion for the example: the processing transfers and "stitches together" references to people — the postings, amounts, and VAT themselves remain untouched. If after the transfer the figures match but the "Responsible" field is gone — this is exactly the area of responsibility of this mechanism (users need to be mapped), not a sign of data loss. 5. Types of operation The processing handles three technical operations: - Reference collapsing during upload — direct references to users in separated data are replaced with a neutral representation. - Reference restoration/mapping during loading — neutral references are bound to the users of the recipient database. - Maintenance during data area transfer — reconciliation of user references between separated and unseparated data within the service technology. 6. What is generated upon posting A key point, so as not to look for something that doesn't exist: - There are no accounting postings. The processing does not make movements on accounts 1210/1030/3310/3130 etc. - No electronic invoices (ESF) or waybills (SNT) are generated. Electronic documents (IS ESF, SNT) are created by sale/receipt documents, not by the service transfer mechanism. - There are no movements in accounting registers (sales, cost of goods, mutual settlements). - What actually changes: the values of reference fields of the "User" type (Responsible, Author, Modified by) in the transferred objects and their reflection in the upload/load file. Plus — service entries in the registration log about the progress of upload/loading. 7. Printed forms There are no printed forms. This is a service processing of the data separation technology; it does not print an invoice, a waybill, or an act. Printed forms (including ESF) belong to accounting documents — sales, receipts, invoices. 8. Common errors Message / symptom Cause How to fix "Insufficient rights to perform the operation" The processing was opened under a regular user Run under an administrator with data administration rights "This operation is only available in the service model" / methods unavailable Attempting to run the collapsing in a regular (unseparated) file database Do not run it directly in the boxed installation — the mechanism is designed for a data area in the service model After loading, "Responsible / Author" fields are empty The recipient database has no corresponding users — there is nothing to bind the reference to Set up users with the same names before loading, or map them manually afterward "Data area upload file not found" Incorrect path/corrupted archive specified Check and re-specify the correct upload file Loading into a non-empty area: conflicts and duplication The recipient area was not cleared Load into a clean data area 9. FAQ Does an accountant need to run this processing themselves? No. It is called automatically when uploading/loading a data area. It only makes sense for an administrator to open it manually for diagnostics. Does it change amounts, VAT, or postings? No. It only touches user references. Amounts, the 16% VAT rate, cost of goods, and postings remain unchanged. Does it generate ESF or SNT? No. Electronic documents are generated by accounting documents (sale, receipt), not by the service transfer mechanism. Why did the "Responsible" persons disappear after the database transfer? Because the new database did not have the same users, and there was nothing to bind the neutral references to. Set up users with the same names before loading, or map them afterward. What is "collapsing of user references"? Replacing a direct internal reference to a user with a neutral representation independent of a specific information base, so that after loading the reference can be restored. Does the processing work in a regular unseparated file database? Normally — no. The mechanism is designed for the service model (separated data). In a boxed unseparated database its methods are unavailable or useless. Does it have a printed form or a report? No. It does not produce either printed forms or accounting reports. Can the processing corrupt data during transfer? It does not change the accounting data itself. The only risk is incorrectly restored user references, which is fixed by mapping. Always make a backup copy before uploading/loading. Where can you see that it has worked? In the registration log during the upload/loading of the data area — service events of the transfer are recorded there. Does it affect user rights and settings? It reconciles user references, but roles and rights settings are transferred by separate mechanisms of the service technology; user mapping after loading needs to be checked manually. 10. Related documents and mechanisms - Data area upload/loading (service model tools, 1C:Fresh) — the main scenario within which the processing operates. - "Users" catalog and authentication data in unseparated data — what the collapsed references are matched against. - Accounting documents (Sale of Goods and Services, Receipt of Goods and Services, Invoice/ESF) — sources of the "Responsible/Author" fields that are processed during transfer. It is they that generate postings and electronic documents, not this processing. - Backup / export to file — a mandatory accompanying step before any transfer. How to find out your release. "Help" → "About the program": it shows the platform version and configuration release. Check compliance — the behavior of data separation service mechanisms depends on the version. Material prepared for "Trade Management for Kazakhstan", release 3.4.5.21 (edition 3.4). --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_