Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You configured synchronization with "1C:Trade Management" or transferred the database to a new release. Suddenly, in the service list, in the filter or in the error exchange text, a strange name flashed — "DeleteDataExchangeSettings". The first thought: is this garbage? Can I clean this up? Will the exchange break if I touch it? Calm down. Below is what this object actually is, why it has such a name, and what you should do with it (spoiler: almost nothing).
1. Purpose
This is a service directory of the "Data Exchange / Data Synchronization" subsystem. It once stored technical settings for exchanges between 1C information databases. The prefix "Delete" in the name is a convention of 1C developers: this marks objects that are decommissioned and left in the configuration only temporarily, so that old data can be correctly transferred during updates. You do not need to work with it manually.
Important: this is not an accounting document. It does not calculate VAT, PIT, WPT, does not generate electronic invoices (ESF) or tax returns (SNT) and does not make postings. Therefore, tax rates and amounts (VAT 16%, MRP 4,325 ₸, etc.) have no relation to it — do not look for accounting here.
2. Where to find
In the regular accountant interface, this directory is not available in the menu — and that is correct, it is a service object. You can only open it directly:
- Menu "Service and Settings" (icon ≡ in the upper right corner) → "Functions for Technical Specialist" (the mode must be enabled in "Administration");
- or through the navigation link.
1C Navigation Link (Main Menu → "File" → "Open" is not available for links; use "Service" → "Go to Navigation Link", paste the line):
e1cib/list/Directory.DeleteDataExchangeSettings
The live (current) synchronization settings that you are actually working with are located elsewhere: "Administration" → "Data Synchronization".
2a. How to know your release
"Help" → "About Program" (or "Service and Settings" → "About Program"). In the opened window, you will see:
- platform version (for example, 8.3.24.xxxx) — this is the "engine";
- configuration release — for example, "Accounting for Kazakhstan, version 3.0 (3.0.74.2)".
It is the configuration release that determines which version this instruction refers to. If your release is older or newer — the composition of service objects may have changed.
3. How to "fill"
Honestly: you do not fill this in manually and should not fill it in. Records here were automatically entered — during the setup or transfer of data exchange. The fields are technical in nature and serve the synchronization mechanism, not user input.
What you might actually encounter in the record (typical set for the service data exchange directory):
| Field | Purpose | What happens if you touch it incorrectly |
|---|---|---|
| Name | Human-readable name of the setting/exchange node | You will stop recognizing the record in the lists; it does not affect the exchange itself |
| Code | Technical identifier | Manual changes may "detach" the record from references in the exchange registers |
| Reference to exchange plan/node | Connection to a specific exchange | Broken connection → the exchange will not find its setting |
| Deletion mark | Indicator "to the trash" | Mark the necessary record — an error may occur during the next synchronization |
The exact composition of attributes in version 3.0.74.2 is version-specific and requires verification in the configurator of your database. But the conclusion is the same: the user has nothing to edit here.
4. Analyzed example
The directory does not have postings — it does not create them. Therefore, let's analyze a real scenario for which you actually ended up here.
Situation. You updated from 3.0.6x to 3.0.74.2. After the update, you opened "Administration" → "Data Synchronization" and saw a warning that some old exchange settings were transferred to a deprecated object.
What happens "under the hood":
- The old exchange setting (for example, with "Trade Management") during the update was copied to the record of the directory
DeleteDataExchangeSettings— as an archive. - The working setting was created in the new mechanism — "Data Synchronization Settings" (standard subsystem of BCP).
- The exchange continues through the new mechanism. The old record simply remains as ballast.
What you do (step by step):
- Check that the exchange works: "Data Synchronization" → "Synchronize". If the data is flowing — everything is fine.
- Do not touch the old record. It will be removed by the developer during scheduled maintenance of the configuration (in one of the future releases, the object will be completely deleted).
- If the record interferes (duplicates in the exchange report) — mark it for deletion only after you have confirmed that the working setting exists in the new mechanism, and perform "Administration" → "Delete Marked Objects" with reference control.
No amounts, accounts 1210/3310/6010, or electronic invoices (ESF) arise here — this is purely a technical transfer of settings.
5. Types of operations
Like a regular directory — not "types of operations," but actions on elements:
- Create (not recommended — new exchanges are configured in another mechanism);
- Copy;
- Mark for deletion / Unmark;
- Open/Edit (for viewing only).
None of these actions generate accounting or tax movements.
6. What is formed when posted
Nothing. The directory is not posted (documents are posted, not directory elements). Accordingly:
- there is no debit/credit posting;
- electronic invoices (ESF) and tax returns (SNT) are not generated;
- there are no movements in accounting and tax registers.
The only thing the record may influence is the service information registers of the exchange subsystem (object correspondences, data versions). This is internal "kitchen" of synchronization, it does not concern reporting.
7. Printed forms
There are no printed forms. This is a service directory — there is nothing to print from it.
8. Common errors
"Data exchange setting not found" / "Synchronization setting not found". Reason: the working setting has moved to a deprecated object, and a new one was not created (break during the update). Solution: "Administration" → "Data Synchronization" → "Configure Data Synchronization" again; then mark the old record for deletion.
"Object cannot be deleted as there are references to it". Reason: you are trying to delete a record that is still referenced by exchange registers. Solution: first complete/delete the exchange itself in the new mechanism, then delete the service record through "Delete Marked Objects" with reference analysis.
"Insufficient rights to view the directory DeleteDataExchangeSettings". Reason: the user does not have administrator/technical specialist rights. Solution: open under a user with full rights.
Double synchronization / data arrives twice. Reason: both the old (deprecated) and the new setting are active simultaneously. Solution: keep only the setting in the new mechanism, mark the deprecated one for deletion.
9. FAQ
(See the FAQ block — questions and answers match.)
10. Related documents
- "Data Synchronization Settings" ("Administration" → "Data Synchronization") — active mechanism that has replaced it. This is where exchanges with "Trade Management," "Retail," website, etc. are configured.
- Exchange plans (service) — define the composition and rules of exchange.
- Information registers of the exchange subsystem — store correspondences and versions of objects.
This directory is not entered by the user based on anything and nothing is entered based on it — it is filled automatically during updates/migrations.
How to know your release
"Help" → "About Program": a line with the platform version (8.3.x) and the configuration release "Accounting for Kazakhstan, version 3.0". If your release differs from the one specified below — check against the updated instruction.
Prepared for release "Accounting for Kazakhstan" 3.0.74.2 (version 3.0).