Data Conversion 3.0 Instructions. And a few words about the set in the group

In this article I will describe my, while small, experience in organizing data exchange through universal enterprisedAdata format.

In my case, the exchange is configured between the configurations "Trade Management 11.2" (hereinafter utilized by UT) and "Company Accounting 3.0.43" (hereinafter referred to as BP). Exchange one-way, from UT in BP. Before updating "Trade Management 11.1" to the version "11.2", the data exchange was configured using the configuration "Conversion of Data 2.0". However, after switching to "11.2", errors have appeared in the "Trade Management". The procedure for updating the exchange rules was carried out, but the result did not give it. The debugger showed that the problem in the exchange of data. It was decided to remove the data exchange settings in both configurations and configure again.

And "Managing Trade", and "Business Accounting" we work in the client-server version. I started setting up synchronization with ut. It performed it in such a way that the data is unloaded from UT to the file. That is synchronization through network catalog. In BP set up the exchange in such a way that no data is discharged from BP.

Error calling a context method (check): XDTO data verification error:
The structure of the object "/ BankingContrigent / Bank" does not correspond to the type: (http://v8.1c.ru/edi/Edi_stnd/enterprisedata/11.1) Conference
Check Properties "Beach":
Form: element
Name: (http://v8.1c.ru/edi/edi_stnd/enterprisedata/1.1 Montebik
a type:
No compulsory property
Object: AgreementTransportant No. ...

To analyze the error, I clicked on the "Composition of the data sent" icon and in the list of counterparties registered to sending contracts found an agreement on which an error appeared. He opened a contract, remembered the counterparty bank account specified in the contract. Then he moved to registered to sending bank accounts. It turned out that the required account is not in the list of registered. I rewrote a problem bank account and contract. After that, I registered the manual bank account.

Repeated an attempt to synchronize data from ut. This time the data was successfully discharged. IN network folder An XML file containing data for transfer from UT to BP has been formed.

The next step is to download data from the file to the enterprise accounting. In the "Business Accounting" configuration, I pressed the "Synchronize" button, the processing form opened with the message analysis. A little later, the message was changed to "data unloading". At the same time, the indicator and counter showed that more than 80 thousand objects are unloaded from BP. It was embarrassed me, because I pointed out in the settings that it should not be discharged from BP. The processing was performed for quite a long time and ended with an error:

Event: Data Exchange
(Common Module. Advisory Operations. Module (371)): the workflow of the background task emercted
Call scores (text errors);

To localize the error, I tried to change the synchronization settings and the Warantrates of the BP base. As a result, when I turned the base in the file, the system worked adequately: a form of matching two databases opened. After mapping objects, initial synchronization has passed successfully. Then I again transferred the database to the client-server option.

With a further "run-in" synchronization, it was required to make some changes to the rules for converting objects. It is time to use the configuration "Conversion of data 3.0". The built-in configuration certificate describes how to work. Also helped articles on the ITS website.

As a result, I downloaded the following data in "Conversion of Data 3.0":

• Texts of the General Module "Managed Independent Format" of two databases
• Scheme of both bases
• Description of Enterprisedata format (from one any database)
• Conversion rules

After downloading, opened the rules for converting data, objects, properties to "data conversion 3.0". Versions needed to me. Then I used the "Upload Module Module Module". The module text was copied to the clipboard. It remains only to insert it into the configuration.

Estiments with the setting of rules in "Conversion of Data 3.0", I concluded that in the case when the acclaimed edits are insignificant, it is easier to customize the rules directly in the configurations of UT and BP, in the General Module "Managed Dane Caulcher." If editors are sulfur, such as, for example, adding a new object in exchange, then you should use the configuration " Conversion of data 3.0 ".

The task of adding the document "Order by the Supplier" to the exchange plan I was performed using " Conversion of data 3.0 ". In the standard version of UT - there is no system of this document in terms of exchange.

We will remember that the rules for registration of objects for unloading are configured in the configuration "Conversion of data 2.0".

These are the first impressions of data synchronization through the universal EnterprisedAdata format.

P.S. If you have questions and your own monitoring of data exchange through universal format and configuration " Conversion of data 3.0, write in the comments. We will exchange experiences.

• Data synchronization
• Universal format EntePrisedata.
• Data Conversion 3.0
• Data Conversion 2.0.
• Trade management
• Accounting company

Conversion of data 2.0 and 2.1 - Technological configuration of the company 1C, implemented on the platform version of 8.1 to 8.3.

The main task of the instrument is to write the exchange rules between the 1C 8 and 7 applied solutions 8. The current version of the data conversion today is 3.0.

Data Conversion is a very useful configuration, using it you can solve not only the issue of information transfer from one information base To another, but also, for example, converting information inside one base.

The configuration is very convenient to use when.

Data conversion will be useful to any programmer: the existence of the skills of creating the exchange rules is a serious plus to professional skills.

To study work with the configuration, the solution is best suited for practical tasks. Try to come up with a task yourself, for example: to transfer any information from one base to another, turn the implementation document to the receipt document, "drive" the current balances on accounting to the "Introduction" and other tasks.

It will be very useful to understand the "typical" regulations of the exchange of 1C 8.3, there often can be found interesting examples implementation of tasks.

To comprehend the basics you will need materials, consider them below.

Video Instructions for Conversion

Aza Data exchange settings in 1C using the "1C data conversion" configuration on the example, see the video:

Materials, textbooks for studying 1C data conversion 2.0

Materials and documentation on the network are not too large, I tried to collect the most important and interesting materials:

0. First of all, I advise the free video course of Ilya Leontiev, it is available on link.

1. I would advise first use the built-in help in the configuration. It is really nicely written and competently implemented technically:

2. The second most important source of information is http://www.mykod.info/ (site closed), specialized just on data conversion. There you can download a large number of Conversion materials.

3. Separately, I would like to highlight the tutorial - (author - Olga Kuznetsova).

The main question arising from a specialist when starting work in the configuration "1C: Data Conversion" Edition 3.0 - What is the difference? What is the difference in the editorial board 3.0 from the editorial office 2.1.
Conditionally differences can be divided into two groups:

• Functional
• Architectural

Architectural differences

Editorial 2.1, the development of the exchange rules were carried out separately for each individual configuration. After that, these rules were used in universal exchange processing in xML format Or to exchange according to the rules between configurations. The output received a file with expansion XML.which contained in addition to these handlers performed on the recipient side. Editorial 3.0 uses a single universal format Enterprisedata. Through which the three main data types are transmitted:

• Regulatory background
• Documentation
• Remains on the date in quantitative or summation

The description of the Enterprisedata format version 1.0 can be viewed. This version of the format includes a description of 94 types of business entities from various business areas. Also note that the format is expandable.

Functional differences

For the possibility of applying the format Enterprisedata. You need to use the version of the library of the standard subsystems not lower than 2.2.5, otherwise only the editors 2.1.
If you need to develop rules for one-time data transfer (or recovery), or transfer residues ... then! Faster and more profitable to use the editorial conversion for development 2.1
But if you want a daily reliable exchange between solutions on the platform "1C: Enterprise" (provided that the BSP version corresponds to), then your choice is "1C: data conversion" Edition 3.0.

Sure! Many will say that to this day, the enterprise uses the exchange in the old format, and every half of the seconds fly gigabytes of data, and everything works and then further further ... certainly works! As many organizations are used to account for the 1C version 7.7 platform. It is important to understand that we are talking about a new format, and that typical solutions use the "Enterprisedata" format, which means to develop in the editorial board 3.0 you need to be able to now.