In this article, we will analyze the basics of data exchange technology using 1C: Data Conversion 3.0 - how it works, what are the advantages, are old exchange technologies relevant.
Many specialists worked with data exchanges in CD 2.0/2.1. Conversion 3.0 introduces a completely new technology. Now we will tell you its essence.
What is the essence of Data Conversion 3.0
Configuration "Data Conversion" was first released by 1C for the 7.7 platform, and since then the data exchange mechanisms have developed within the framework of one approach.
All exchanges between 1C databases with different structures required writing exchange rules.
With this approach, in the Source database, each object undergoes a series of transformations, which are described in the rules created for this pair of databases.
The Xml node into which this object is uploaded is similar in structure to the object in the Receiver database. When loading it, all that remains is to convert it into an infobase object.
In order to create rules, you need to know the structure of the metadata of the Source database and the Receiver database, and describe the transformation of objects of all necessary types. The rules are uploaded to an external xml file, which is used every time it is uploaded.
One of the problems with this approach is that after each change in the configuration of the Source or Receiver databases, it is necessary to check the rules for relevance, which is a long and not always simple process.
Moreover, if the exchange is carried out in both directions, then there are two such rules.
The first version was released in October 2014 "Data Conversions", edition 3.0, intended for testing.
The new technology implemented in Data Conversion 3.0 is designed to separate the processes of uploading and downloading and make them independent. For this purpose, a completely different concept of exchange has been created.
The data will be downloaded in the format EnterpriseData, which does not directly depend on the structure of the Source and Receiver databases.
The EnterpriseData format is an xml format that was created to become universal for all exchanges both between 1C databases and with third-party databases.
It is provided in the form of an xsd scheme, on the basis of which a mechanism for converting objects between this format and any information base objects is formed. To simplify these conversions, the format EnterpriseData contains objects similar to metadata objects of standard configurations.
When exchanging via a universal format, each database contains only code for converting objects from the database to the universal EnterpriseData format and back.
When unloading, information about what structure the recipient databases have is not used.. Therefore, when changing the configuration of each of the databases participating in the exchange, you will need to change this code only in this database.
This code is in the general module . All event handlers and the entire object transformation mechanism are also located there, which greatly simplifies the debugging process. Parameters can also be described there, with the help of which you can use the object conversion logic described there once for exchange with different databases.
If necessary, the developer can change the structure of the EnterpriseData format to solve a wider range of problems.
In the process of setting up the exchange, the “Data Conversion 3.0” configuration itself is currently performing only one function- based on the metadata structure of the databases participating in the exchange and the universal format scheme, it generates the texts of common modules Exchange Manager Through Universal Format for each of the bases.
It will be convenient to create these modules at the initial stages of setting up the exchange, and carry out further modifications directly in the text of the modules in the configurator.
The new exchange mechanism also does not exclude the use registration rules. They are currently configured using the Data Conversion 2.0 configuration.
Thus, the new technology has a number of advantages:
- To exchange between three or more databases, you do not need to create separate rules for each pair of databases
- Support for data exchanges is simplified in case of database configuration changes
- A new universal format has been created that can be used, in particular, for exchange with third-party databases
- The debugging of algorithms used when unloading and loading objects is simplified.
A gradual transfer is planned in the near future everyone exchanges between standard configurations for a new standard.
However, exchange through the Universal Format not considered as a complete replacement exchange technologies according to the rules. “Data conversion” version 2.0/2.1 will continue to be supported, since it remains a more convenient and flexible mechanism for solving a certain range of problems.
To know how KD 3.0 performs data exchange, proceed to the following article – Data conversion 3.0. New technology .
Olga Kuznetsova
1C:Enterprise is the main program that enterprises use for reports, collecting accounting data and much more. The program is constantly being developed and improved, new versions are released, which leads to the need for data conversion. Often, converting data to a new version of 1C:Enterprise causes many problems. How to correctly convert data to newer versions of the program, and how to generally learn how to transfer data between databases of any configuration?
To answer this question, Vadim Sayfutdinov has prepared a free video course “Data conversion - data exchange using 1C databases.”The course contains 6 lessons, designed for 6 weeks, in each of which you need to listen to theoretical knowledge and do independent work. The course can be studied directly on the website or downloaded to your PC. All necessary data will be provided to you absolutely free. To convert data, you will be given access to the project server, and you will be able to practically consolidate your knowledge.
The video course by Vadim Sayfutdinov covers:
- Creation of new rules for exchange between data from 1C:Enterprise databases;
- Converting data between standard 1C programs;
- Exchange between versions 7.7 and 8 and COM AND ONLINE exchanges.
- Video – 21 teaching hours
- Teaching materials in PDF - 117 A4 pages
- 16 practical tasks with teacher solutions
Course format, support
The materials are available immediately after payment for the order - you download them from the site and study them at any convenient time.
Support is provided through the Master Group on the website.
Full access to the Master group must be activated no later than 100 days after purchase.
Relevance of the course
The course materials are relevant for BSP version 2.3.2.73.
If you plan to use older versions of the BSP, then please note that the operating mechanisms of the BSP “Data Exchange” subsystem have changed, and the interfaces have also changed.
A new course for the latest versions of the BSP is under development and will be released in a few months. But for versions of BSP 2.3.2.73 and younger, the current rate will be relevant.
Course fee
9,700 rubles
Guarantee
We have been teaching since 2008, we are confident in the quality of our courses and give our standard 60-day warranty.
This means that if you started taking our course, but suddenly change your mind (or, say, do not have the opportunity), then you have a 60-day period to make a decision - and if you make a return, we return 100% of the payment.
Installment payment
Our courses can be paid for in installments or in installments, including without interest. Wherein You get immediate access to materials.
This is possible with payments from individuals in the amount of RUB 3,000 or more. up to 150,000 rub.
All you need to do is select the payment method “Payment via Yandex.Checkout”. Next, on the payment system website, select “Pay in installments”, indicate the term and amount of payments, fill out a short form - and in a couple of minutes you will receive a decision.
Payment options
We accept all major forms of payment.
From individuals– payments from cards, payments with electronic money (WebMoney, YandexMoney), payments through Internet banking, payments through communication shops, and so on. It is also possible to pay for the order in installments (in installments), including without additional interest.
Start placing your order - and in the second step you can choose your preferred payment method.
From organizations and individual entrepreneurs– cashless payment, delivery documents are provided. You enter an order and you can immediately print an invoice for payment.
Training of several employees
Our courses are designed for individual learning. Group training on one set is illegal distribution.
If a company needs to train multiple employees, we typically offer “add-on kits” that cost 40% less.
To place an order for an “additional kit” select 2 or more course sets in the form, starting from the second set the cost of the course will be 40% cheaper.
There are three conditions for using additional kits:
- You cannot purchase only an additional set if at least one regular set was not purchased before (or along with it)
- There are no other discounts for additional sets (they are already discounted, it would be a “discount on a discount”)
- promotions are not valid for additional sets (for example, compensation of 7,000 rubles) for the same reason
Automated control systems in most cases consist of separate databases and often have a geographically distributed structure. At the same time, correctly implemented data exchange is a necessary condition for the effective operation of such systems.
The initial setup of the exchange may require a number of actions, not only in terms of programming, but also consulting, even if we are dealing with homogeneous sources, as is the case with products on the 1C:Enterprise platform. Why setting up 1C exchange (or, as it is also called, data synchronization in 1C 8.3) can become the most time-consuming and expensive task of an integration project, we will look at in this article.
Data exchange in the 1C environment allows you to:
- Eliminate double entry of documents;
- Automate related business processes;
- Optimize interaction between distributed departments;
- Promptly update data for the work of specialists from different departments;
- “Differentiate” between different types of accounting.*
*In cases where the data of one type of accounting differ significantly from another, it is necessary to ensure the confidentiality of information and “delimit” information flows. For example, data exchange between 1C UT and 1C Accounting does not require uploading management data into the regulatory accounting database, i.e. synchronization in 1C will be incomplete here.
If we imagine the standard process for implementing primary data exchange, when at least one of its objects is a 1C product, then we can distinguish the following stages:
- Coordination of the composition of the exchange;
- Definition of transport (exchange protocols);
- Setting rules;
- Scheduling.
Identification of the composition of 1C exchange
Objects of exchange can be divided into “source” and “receiver”. At the same time, they can perform two roles at the same time, which will be called a two-way exchange. The source and destination are determined logically depending on the need or the functionality of the system.*
*For example, when integrating “WA: Financier” - a solution for maintaining financial accounting and managing treasury processes, developed on the basis of “1C:Enterprise”, WiseAdvice experts recommend it as a master system. This is due to the availability of control tools to comply with the rules of the application policy, and, accordingly, to ensure the effectiveness of the solution.
Next, based on the received and recorded requirements from users, a list of data for exchange is created, its volume, requirements for the frequency of exchange are determined, and the process of working with errors and handling exceptional situations (collisions) is prescribed.
At the same stage, depending on the fleet of existing systems and the structure of the enterprise, the exchange format is determined:
Distributed information base
- RIB implies exchange between identical 1C database configurations, with a clear “master-slave” control structure for each exchange pair. As an element of a technology platform, RIB, in addition to data, can transmit configuration changes and administrative information of the database (but only from master to slave).
Universal data exchange in 1C
- A mechanism that allows you to configure the exchange of 1C databases, both with configurations on the 1C:Enterprise platform and with third-party systems. The exchange is carried out by transferring data into a universal xml format in accordance with the “Exchange Plans”.
EnterpriseData
- The latest development of 1C, designed to implement data exchange in xml format between products created on the 1C:Enterprise platform with any automation systems. The use of EnterpriseData simplifies the modifications associated with the exchange. Previously, when a new configuration was included in a system, it was necessary to implement a mechanism for importing and exporting data, both for it and for existing systems. Now systems that support EnterpriseData do not need any modifications, having only one entry-exit point.
Definition of transport (exchange protocols)
For the system on the 1C:Enterprise 8 platform, a wide range of possibilities is provided for organizing exchange with any information resources using generally accepted universal standards (xml, text files, Excel, ADO connection, etc.). Therefore, when determining the transport for exchange data, you should rely on the database capabilities of the third-party system.
Synchronization of directories
The basic principle of effective synchronization of directories is the presence of a single entry point. But if we are talking about working with directories that have historically been filled out according to different rules, it is necessary to clearly define synchronization fields to bring the exchange to a “common denominator.”*
*At this stage, it may be necessary to carry out work to normalize the reference data on the side of the data source. Depending on the state of the directories and their volume, the process of comparing elements, recognizing, identifying errors and duplicates, as well as filling in missing fields and assigning synchronization fields, may require the work of a whole group of experts, both on the part of the integrator (the owner of the master data normalization technique) and from the customer's side.
Setting rules
The ability to display data from source systems in receivers depends on correctly defined exchange rules. The rules, presented in xml format, regulate the correspondence of key details of source-receiver objects. The 1C:Data Conversion solution is designed to automate the creation of rules for implementing both one-time and permanent exchanges.
Guarantees no data loss during exchange Exchange Plan. This is an integral part of any configuration on the 1C:Enterprise platform, which fully describes the 1C exchange procedure: data composition (documents with “identifying” details) and nodes (receiver-transmitter information bases), as well as activation of RIB for selected exchange directions.
Any change in the data entered into the Exchange Plan is recorded and receives the “changed” sign. Until the changed data matches each other in the receiver-transmitter nodes, the sign will not be reset, and the system will send control messages to both nodes. After uploading the data and confirming their full compliance in both systems, the sign is reset.
Exchange schedule in 1C
To automate regular exchange, the frequency of data uploading is set. The frequency of exchange depends on the need and technical capabilities. Also, configurations on the 1C:Enterprise platform allow you to configure data exchange when an event occurs.
Having considered the standard process of implementing an exchange, let’s pay attention to factors that will require improvements at different stages:
- Non-standard, highly modified database configurations;
- Different versions of the 1C:Enterprise platform;
- Configuration versions that have not been updated for a long time;
- Objects of exchange that have previously undergone modifications;
- The need for non-standard exchange rules;
- A very different set and composition of details in existing reference books.
Since even standard actions to implement primary data exchange require expert knowledge, they are recommended to be carried out with the participation of 1C specialists. Only after completing all the steps described above should you proceed to setting up the exchange in the configuration. Let's look at the integration of databases using the example of 1C:UPP and 1C:Retail (exchange with 1C:UT is set up using the same scheme). Also included in standard synchronization is the SCP - SCP exchange, which is typical for large-scale automation systems at the largest industrial enterprises.
In the “Service” submenu, select “Data exchange with products on the platform...” (selecting direct exchange with “Retail” often results in errors at the level of COM objects). Please note the service message “This feature is not available.”
To resolve this issue, you need to select "Configure Communications"
...and check the box. Next, ignore the error message.
In the data synchronization settings, select “Create an exchange with “Retail”...
Before configuring connection settings through a local or network directory, you should make sure that there is space on the disk for the directory. Although, as a rule, it does not take up more than 30-50 MB, in exceptional cases it may require up to 600 MB. You can create the required directory directly from the configurator.
When connecting via a network directory, we ignore the offer to configure the connection via an FTP address and by email by clicking “Next”.
In the settings, we manually enter prefixes - symbols of the databases (usually BP, UPP, RO), set the rules and the start date for data upload. The prefix will be indicated in the name of the documents to indicate the database in which they were created. If the upload rules are not edited, the data will be uploaded by default according to all available parameters.
We create an exchange settings file for “Retail” so as not to repeat our actions. If you need to immediately send data immediately after setting up synchronization, check the box.
To automate the exchange process, you need to set up a schedule.
Menu "Retail".
Check the box and select “Synchronization”.
We perform the “reverse” setup by selecting Production Enterprise Management.
Load the settings file created in UPP.
We put a tick, the system picks up the address automatically.
We act in the same way as in UPP.
Verification data comparison (Manual data comparison is recommended to be done at the preparatory stage, since this work can become the most labor-intensive in the process of implementing the exchange). The comparison window opens by double clicking the mouse.
In case of an error in synchronization, “Details...” will be replaced with “Never...”.
“Details...” opens the log with updated information on the exchange.
Ready.
Note: The lesson presents screenshots for the 5.x exchange module. For module 6.x they are similar.
The form for creating/editing an exchange node looks like this:
By button Execute data exchange There is a normal exchange of data with the site according to the specified settings.
When you press the button Forced full data download In addition to the usual data exchange, all product images can be downloaded, and a unique version of the product can also be downloaded.
Name And Code will be filled in automatically when saving the settings. But you can set them manually if necessary.
On the bookmark Setting up sharing options basic settings for exchange parameters are set:
Purpose
- When selecting the option Uploading to the site the data will be uploaded to the website, the connection settings for which are specified in the appropriate fields:
- Website address– the address of your website, containing the path to the file /bitrix/admin/1c_exchange.php (or the path to the page with your own integration settings, see the lesson Own integration settings).
- Username– login of the user of the site under control "1C-Bitrix: Site Management". The user must have the right to perform data exchange, i.e. the user must belong to the group specified in the integration settings.
- Password– user password.
- If the option is checked Upload to a directory on disk, then the data will be uploaded to a directory on the disk. The exchange catalog and order loading file are specified in the appropriate fields.
Log storage
In field Log directory the directory in which the exchange log file will be stored is specified. Logs are stored by day in a subfolder reports. In addition, using the options of the same name, you can determine whether to upload logs to the site and whether to store exchange files on the site.
Actions with failed packages:
- In field Number of retries for unsuccessfully sent packets indicates the number of attempts to send a data packet if the packet was sent unsuccessfully.
- In field Timeout between retries of unsuccessfully sent packets specifies the number of seconds that must pass before the exchange resends a failed data packet.
- If the option is checked Continue sending failed packets on next exchange and there are unsuccessfully sent packets, then during the next exchange, the unsent packets will first be unloaded, and then the exchange itself will occur.
Setting up auto exchange:
If the option is checked Use periodic data exchange then the exchange will be performed according to the specified schedule. Depending on the base 1C in the file or client-server version, the auto-exchange setting is different.
When you check this box, a form for setting up an exchange schedule will automatically open, in which you can set the start and end time of the exchange, the start and end date, and the frequency. For example, for the schedule to be executed every day, in the field Repeat every there should be a value 1 day.
In additional settings, you specify the user who is substituted into the data (the form opens by clicking Additional schedule settings):
Note: if base 1C in the file version, you must specify the user under whom the auto-exchange will be performed in the accounting settings settings ( Operations > Constants, tab Data exchange ):
On the bookmark Communication mode settings for the data exchange mode are specified:
A checked option means that the exchange setting is used for real-time exchange.
Important!
- Only orders can be exchanged in real time.
- Only one setting can have the option checked Used in real time.
Uploading information about items
Checked option Activate activates settings for unloading goods and information about them. By button Tune The corresponding settings window opens.
Uploading user directories
Checked option Activate activates settings for uploading user directories to Highload blocks on the site. By button Tune the corresponding one opens
Loading...
