“УдалитьНастройкиОбменаДанными” Catalog — Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog is intended to store settings for synchronization and data exchange between 1C infobases: FTP and email transport parameters, online connection to a remote database, logging, and automatic exchange modes. The object belongs to the former universal data exchange mechanism and is retained in the configuration to support previously entered settings and process them during updates.

Important. In current releases of “Accounting for Kazakhstan”, synchronization tasks are performed using the “Data Exchange” subsystem: through exchange plans, synchronization settings, and formats supported by the configuration. New settings should not be created in the УдалитьНастройкиОбменаДанными catalog. Work with this object is classified as an administrative and service operation.

Where to find it in 1C. “Universal Mechanisms” section → “Delete Data Exchange Settings”. For direct access, use the link e1cib/list/Справочник.УдалитьНастройкиОбменаДанными.

2. Header attributes and tabular sections

2.1 Header attributes

The attributes can be grouped into functional blocks:

• FTP transport — FTPАдресОбмена and related connection parameters included among the object’s attributes.

• Email transport — АвтоматическиЗакачиватьПочтуПриОбмене and АдресДляОтправкиСообщенийОбОшибке.

• Online connection to a remote database — OnLineОбмен, АутентификацияWindowsИнформационнойБазыДляПодключения, ВерсияПлатформыИнформационнойБазыДляПодключения, ИмяИнформационнойБазыНаСервереДляПодключения, ИмяСервераИнформационнойБазыДляПодключения, КаталогИнформационнойБазыДляПодключения, and ИмяФайлаПротоколаОбменаOnLineОбмен.

• Logging and automatic exchange modes — ВестиЛог, ВопросПриАвтообмене, attributes for displaying messages during automatic exchange, and ВыполнятьАрхивациюФайловОбмена.

• Privileges and processing of imported objects — ВыполнятьДействияПодПолнымиПравами, ВыполнитьОтложенноеПроведениеДокументовПоРасписанию, and ДобавлениеОбъектовИзФоновогоОбмена.

In addition to the listed attributes, the object has the standard catalog fields: Code, Description, Deletion Mark, Predefined, and Ref.

2.2 Tabular sections

No separate tabular sections are specified in the object structure shown. Transport, connection, logging, and automatic exchange parameters are represented by header attributes. Exchange-related information may be stored in other configuration objects accessed by service mechanisms. Therefore, when maintaining the infobase, refer to the actual metadata structure of release 3.0.74.2 and analyze the catalog’s links to exchange plans, information registers, and synchronization data processors.

3. Forms

The set of forms for this service catalog is designed for viewing and administering saved settings:

If the object has no dedicated form assigned for the relevant type, the 1C platform uses a form generated according to standard rules. The actual list of assigned forms, their commands, and their elements are determined by the metadata of the “Accounting for Kazakhstan” configuration version 3.0.74.2.

4. Key module procedures

The exact procedure names should be taken from the object, manager, and form modules in the configurator for release 3.0.74.2. When maintaining the catalog, first analyze the handlers for writing, fill validation, opening forms, and changing exchange mode attributes.

Object module:

• The before-write handler may be used to reconcile connection parameters before saving an item.

• The fill-check handler may validate attributes required for the selected transport or connection option.

• Write and deletion handlers may account for references to the setting from other objects of the exchange mechanism.

Manager module:

• The manager module may contain functions for retrieving settings by reference and passing parameters to service exchange mechanisms.

• If the configuration provides for selecting a form based on conditions, the relevant logic may also be executed at the manager level.

Form modules:

• When the form is created on the server, the availability of FTP, email, and online connection attribute groups may be configured.

• Mode flag change handlers may control the availability of related form fields.

• Form commands may support administrative operations provided by the former exchange mechanism.

Because the object has a deprecated name with the “Удалить” prefix, its actual calls must be traced before making changes. To do this, search in the configurator for references to the catalog, its attributes, and exported procedures, and then compare the calls found with the current synchronization mechanism.

5. Posting and register records

The catalog is used to store exchange parameters. Posting applies to documents that are imported into the infobase or changed as a result of synchronization. They are processed according to the algorithms of the relevant configuration documents.

The settings have an indirect effect when documents are imported through an exchange. Imported sales, purchase, banking transaction, E-invoice, and ACN documents are processed according to the procedure prescribed for each type. The ВыполнитьОтложенноеПроведениеДокументовПоРасписанию attribute controls the deferred document processing scenario if this mechanism is used in the configuration.

When maintaining an exchange, it is important for an accountant to distinguish between two levels: the catalog stores technical connection and operating-mode parameters, while accounting data is recorded by documents imported into the infobase. After an exchange, check the completeness of the import, document statuses, posting results, and log messages.

When investigating discrepancies, check the following in sequence:

1. which setting and exchange channel were used;

2. whether the file or data package import was completed successfully;

3. whether the relevant document was created or found in the receiving infobase;

4. whether the prescribed document processing was performed immediately or on schedule;

5. whether the exchange log contains error messages and object identifiers.

Electronic documents, including E-invoices and ACNs, are processed during synchronization as related objects of the relevant subsystems. To analyze the result, use the status of the electronic document itself, the data of the related accounting document, and the event log.

6. Related objects and create based on

• Exchange plans — describe the nodes and data included in a distributed exchange in scenarios where they are used.

• Exchange subsystem information registers — may store service states, object mappings, and information about sessions and synchronization boundaries.

• Data exchange rules — define the processing of exported and imported objects for the relevant integration scenario.

• Current “Data Exchange” subsystem — used to configure new synchronization scenarios in the current configuration release.

• Imported accounting documents — sales, purchases, bank and cash documents, E-invoices, ACNs, and other objects included in a particular exchange.

Create based on is not part of the primary purpose of this service catalog. A setting is created and used as an independent item of the exchange mechanism, while links to other objects are implemented by configuration tools.

7. Extension points

• Configuration extensions. If necessary, the interface can be adapted or validation of legacy data can be added; however, modifying a deprecated object increases the solution’s dependence on that object being retained in future versions.

• Object and manager module handlers. If the relevant procedures are available, they may be used for additional validation of transport parameters and for retrieving the setting through service mechanisms.

• Event subscriptions. Suitable for recording changes to catalog items without directly modifying the main configuration.

• Current exchange mechanisms. New integration logic should be placed in the objects and handlers of the current synchronization subsystem rather than linked to an object whose name begins with the “Удалить” prefix.

Implementation specialist’s recommendation. Do not create or replicate new settings in the УдалитьНастройкиОбменаДанными catalog. Use it when maintaining previously entered parameters and migrating current scenarios to the current exchange mechanism. Before changing legacy items, record their values, schedule, connection method, and related nodes.

Questions and answers

• What is this catalog, and what is it used for? УдалитьНастройкиОбменаДанными is a service configuration object that stores parameters of the former exchange mechanism: FTP, email, remote database connection, logging, and automatic startup settings.

• Why does the name contain the “Удалить” prefix? This prefix indicates that the object belongs to a deprecated part of the configuration and has been prepared for subsequent removal. It is retained to process previously created data and related scenarios.

• Can this catalog be used to configure new integrations? For new integrations, use the current tools of the “Data Exchange” subsystem in the “Accounting for Kazakhstan” configuration version 3.0.74.2.

• Who works with this catalog? Work with it is part of infobase administration and maintenance. An accountant may need the object when analyzing synchronization errors, restoring parameters of a legacy exchange, or monitoring document imports.

• How is the catalog related to accounting documents? It stores technical exchange parameters. Documents imported during synchronization are processed using the tools of the corresponding document types. During diagnostics, the import result and the status of each accounting document must be checked separately.

• Where can the catalog be found in the 1C interface? If the command is available to the user, the catalog can be opened from the “Universal Mechanisms” section or via the navigation link e1cib/list/Справочник.УдалитьНастройкиОбменаДанными.

• Should this catalog be customized through an extension? Local changes required to maintain legacy data, such as additional fill validation or change auditing, are acceptable. New synchronization logic should be implemented using the current exchange subsystem.

Conclusion

The УдалитьНастройкиОбменаДанными catalog is a deprecated service object of the “Accounting for Kazakhstan” configuration, edition 3.0. In version 3.0.74.2, it is used when maintaining previously created exchange settings. The specialist’s practical task is to keep current scenarios operational, monitor import results, and gradually migrate integrations to the current synchronization mechanism.