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

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

Data conversion is a very useful configuration, with the help of it you can solve not only the issue of transferring information from one infobase to another, but also, for example, converting information within one database.

The configuration is very convenient to use when.

Data conversion will be useful to any programmer: having the skills to create exchange rules is a serious plus to professional skills.

To learn how to work with configuration, solving practical problems is best suited. Try to come up with tasks for yourself, for example: transfer any information from one database to another, turn a sales document into a receipt document, “drive” current accounting balances into a “balance entry” document and other tasks.

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

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

Video conversion instructions

The basics of setting up data exchange in 1C using the "1C Data Conversion" configuration, for example, see the video:

Materials, textbooks for studying 1C Data Conversion 2.0

There are not too many materials and documentation on the net, I tried to collect the most important and interesting materials:

0. First of all, I advise Ilya Leontyev's free video course, it is available at link.

1. I would advise you to use the built-in help in the configuration first of all. It is really well written and technically well implemented:

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

3. Separately, I would like to highlight the manual - (by Olga Kuznetsova).

The effective operation of 1C Enterprise 8.3 programs is due to the correct configuration of data exchange between them, that is, unloading and loading directories, as well as other information. In some situations, it is enough to use the "Universal exchange XML data»Or the existing standard rules for transferring, for example, when switching from one edition of programs to another. They can be built into the program with a specific list of exchange rules or be in the folder installed update... For example, AccountingBase ("Accounting", basic version) and there is the "Data Exchange" folder.

Fig. 1

But when you need an exchange between completely different configurations, and therefore transfer rules for atypical versions, for which you will need to set up exchange rules and match objects for transfer, you should resort to an external program designed to create conversion rules between any configurations, regardless of their structure and complexity.

To describe the metadata, external processing MD83Exp.epf is used - for products based on the 1C: Enterprise 8.3 platform (managed application), MD82Exp.epf - for a regular application, in XML file format. Usually the processing files are located in the templates directory where the configuration is installed. For example, C: \ Program Files \ 1cv8 \ tmplts \ 1c \ Conversion \ 3_0_5_3 \. In our example, 1C: Data Conversion, ed. 3.0 "(release 3.0.5.3).

Fig. 2

Preparation of the conversion file consists in generating an XML file of exchange rules. Consider at small example the course of its creation.

Step 1. The program can be downloaded from the ITS website or installed from the ITS disk. Suppose we need to unload the "Contractors" directory from "Accounting" to "UT 8.3". The first program we have is "Base-source", and the second is "Base receiver". Note that the exchange is configured not only between 8.3 bases, but also between 7.7 and 8.3 and others.

Step 2. We unload in XML file the structure of the metadata of the databases involved in the exchange using MD83Exp.epf processing. To do this, in the "Base-source" and "Base-receiver" in the "1C Enterprise" mode, open the specified processing and use it to unload the configuration structure, specifying the name of the generated file. For example, let's call the files “Base source” and “Base receiver”.

Fig. 3

Fig. 4

Fig. 5

Step 3. We export the xml-schema of the exchange format. It is a file with the extension "xsd". You can get it both from the "Source" and from the "Receiver". To do this, open the infobase in the "Configurator" mode ("Open configuration"), the "General" section in the metadata tree and the XDTO packages subsection.

Fig. 6

Let's find lines with the name "EnterpriseData" (different numbers are different versions format) and by pressing right click mouse, select the command "Export XML Schema".

Fig. 7

Fig. 8

Fig. 9

Step 4. Add the structure of the database of unloaded configurations (source and destination) to the "1C: Data Conversion" database. To do this, in the "Configuration" menu item for each generated file (source and destination), we perform "Load configuration structure".

Fig. 10

We indicate the path to our file, select the download method - "In new version configuration ", and click the" Execute download "button.

Fig. 11

Fig. 12

After downloading the files, if we go to the "Configurations" section of the menu, we will see our two loaded configurations.

Fig. 13

Fig. 14

Step 5. We load the structures of the exchange format. In the menu item "Data format" select the command "Load format structure".

Fig. 15

Specify the previously uploaded file and click the "Download" button.

Fig. 16

After the download is complete, check the result. Let's go to the menu "Data format" - "Format objects tree". Having selected the format we have loaded, we see its structure.

Fig. 17

Step 6. Conversion creation. To accomplish the task set by us, we create two conversions. The first one is for unloading the “Employees” and “Contractors” directories from “Accounting”, and the second one is for loading into “UT”. Let's go to the "Conversion" menu.

Fig. 18

For each operation, we indicate the name, for example - "Unloading from BP", "Loading into UT", the name - Enterprise Accounting, Trade Management and the version of the format (which we downloaded, in our example 1.6).

Fig. 19

Fig. 20

Step 7.

Fig. 21

Having opened each operation separately, let's configure it. On the "Rules for converting objects" tab, click the "Create" button.

Fig. 22

On the "Basic Information" tab, we indicate the identifier of our rule (for example, Directory_Contractors_Download), a configuration object and a format object. Scope - "For sending".

Fig. 23

Fig. 24

We press "Auto-matching", and by pressing the button "Create rules for converting properties" we save the result.

Fig. 25

Fig. 26

Fig. 27

If necessary, other fields are manually configured for conversion.

Step 8. The conversion rule for upload is configured in the same way, in our example, in "Trade management". Please note that the field of application is "For receiving".

Fig. 28

On the "Properties conversion rules" tab, we perform auto-matching and, by clicking the "Create properties conversion rules" button, save the result.

Fig. 29

Step 9. In both created conversion rules, create a rule for converting predefined data by going to the tab of the same name, clicking the "Create" button, while comparing the values ​​in the table from the configuration and format. Scope - "For receiving and sending."

Fig. 30

Fig. 31

Fig. 32

We indicate a new rule for converting the property "LegalPhysicalFace" for our directory. Let's open the conversion rule for the "Directory_Contractors_Download" object.

Fig. 33

On the "Properties conversion rules" tab, add a property conversion rule, specifying "Enumeration_LegalPhysicalPerson" in it.

Fig. 34

Fig. 35

The action is the same for the second rule "Directory_ContraNet_Loading".

Fig. 36

Step 10. We create a data processing rule. The actions are the same for both rules we created. Going to the conversion rule, click the button "Create based on" - "Data processing rule".

Fig. 37

The data goes into it automatically.

Fig. 38

Fig. 39

Fig. 40

Step 11. Unload the module of the exchange manager, either in the conversion rule by clicking "Save the module of the exchange manager", or through the item "Conversion" - "Unload the module".

Fig. 41

Fig. 42

Fig. 43

Next, we open the configuration for which our module is intended, and in the metadata tree we look for "Change Manager Via Universal Format", open it and paste our copied module into the clipboard there.

Fig. 44

When setting up an exchange, the program in question has so far the only function - the formation of texts common modules ExchangeManagerThrough the UniversalFormat for each of the bases, using the metadata structure of the configurations involved in the exchange and the universal format schemas. It is better to form and use these modules at the initial stage of setting up the exchange, and you should continue to refine them right in the text of the configurator module.

Configuration edition "Data Conversion 3.0" is a new, but progressive technology to simplify the exchange between configurations using the universal exchange format EnterpriseData.

Books, brochures, articles

1C: Enterprise 8. Data conversion: data exchange between applied solutions (with an application on CD-ROM) (article 4601546049094)

"1C: Enterprise" is a universal system for automating enterprise activities and can be used to solve various management and accounting tasks. Currently, a large number of standard and specialized solutions have been developed on the 1C: Enterprise platform, which can work in close integration with other solutions, both on this platform and with software third party manufacturers.

Great value for effective work has the ability to organize an exchange between various information systems. The 1C: Enterprise platform provides a variety of tools for data exchange and integration of applied solutions.

The book describes in detail the exchange of data in the XML format, which is today a generally accepted means of presenting data. The procedures for developing rules are described, the application of which will ensure the transfer of information from one information system to another, including data exchange between typical 1C: Enterprise configurations.

The book is accompanied by a CD containing demo information bases with examples of exchange rules and the configuration "1C: Enterprise. Data Conversion".

Attention! In the first edition, a technical defect was allowed at the end of the book. The corrected pages can be

Currently, the remnants of the marriage are withdrawn from sale and a revised edition has been released.
We apologize for the inconvenience caused and are ready to replace defective copies free of charge.

Questions on the literature of the publishing house "1C-Publishing" can be sent to [email protected].

Buy:

Contact a 1C partner who serves your organization and place an order by informing him of the code assigned to the book (shown in the table below). You can also purchase the book from others partners of the company "1C".

• in the online store "1C-Interest" (delivery of books by courier, "Russian Post", DHL, EMS)
• in bookstores in your city

See also:

Book cost

Code	Name	Recommended retail price, rub. *	Dealer	Permanent partner	Distributor
4601546049094	1C: Enterprise 8. Data conversion: data exchange between applied solutions (with an application on CD-ROM) (article 4601546049094)	240	150	135	120

Book structure

Introduction

Chapter 1. General principles of setting up rules

Chapter 2. Using Rules

Chapter 3. Automatic rule creation

Chapter 4. Structure of the rules

Chapter 5. Detailed study of the rules

Chapter 6. Event Handlers

• Options
• Conversion handlers
• Data Upload Rules handlers
• Object Conversion Rules Handlers
• Property Group Conversion Rules Handlers
• Property Conversion Rules Handlers

Chapter 7. Search Fields

Chapter 8. Data cleansing rules

Chapter 9. Algorithms and Queries

Chapter 10. Typical examples of rules. Workaround

• Converting enumerations
• Converting directories
• Converting documents
• Converting information registers
• Conversion of chart of accounts
• Converting a Chart of Property Types
• Converting a Chart of Calculation Types
• Converting constants 1C: Enterprise 7.7
• Conversion of accounting transactions 1C: Enterprise 7.7

Chapter 11. Rule Optimization

• Data upload rules
• Object conversion rules
• Generic XML Data Interchange Processing

We have been teaching since 2008, we are confident in the quality of our courses and give this course our standard 60-day warranty.

This means that if you started to study in 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 refund, we will refund 100% of the payment.

Installment payment

Our courses can be paid in installments or in installments, including no interest. Wherein you get access to the materials immediately.

This is possible when paying from individuals in the amount of 3,000 rubles. up to 150,000 rubles.

All you need to do is select the payment method “Payment via Yandex.Checkout”. Further on the site payment system choose “Pay in installments”, specify the period and amount of payments, fill out a short questionnaire - and in a couple of minutes you will receive a decision.

Payment options

We accept all major forms of payment.

From individuals- payment from cards, payment by electronic money (WebMoney, YandexMoney), payment via Internet banking, payment via mobile shops, and so on. It is also possible to pay for the order in parts (by installments), including without additional interest.

Start placing your order - and in the second step you will be able to choose your preferred payment method.

From organizations and individual entrepreneurs- cashless payment, documents for delivery are provided. You enter an order - and you can immediately print an invoice for payment.

Multiple employee training

Our courses are designed for one-to-one learning. One-set group training is illegal distribution.

If a company needs to train several employees, we usually offer “add-on kits” that cost 40% less.

To place an order for an "additional kit" choose 2 or more course kits in the form starting with the second set the cost of the course will be 40% cheaper.

There are three conditions for using additional kits:

• it is impossible to purchase only an additional set, if before that (or together with it) at least one regular set was not purchased
• any additional discounts do not apply to additional kits (they are already discounted, it would be a “discount for a discount”)
• additional kits do not have promotions (for example, compensation of 7,000 rubles) for the same reason

Good day, dear blog readers. Previously, this site has already published an article about converting
, this article has shown
how you can set up an exchange using the constructors with which you create exchange rules.
This method can be used when converting databases from 1C version 7.7 to 8.2.
Now we will talk about how to transfer data between 1C 8.2 configurations, which are somewhat different from each other.

The main focus of this article will be on converting the tabular section of the document, which means that
we will work with the rules for converting a group of properties - PKGS.

Preparation for configuring PKGS - rules for converting a group of properties

We will transfer the document "Goods and Services Receipt", which has differences in the VAT rate variable of the "Goods" tabular section
in the source and destination base. In the source database, this variable has the type "ReferenceLink.VAT rates",
and in the base of the receiver - the type "EnumerationLink.VAT rates".

By the way, for convenience, you can define

In addition, in the base of the receiver, we need to fill in the requisite "AccountUchetU", which is also located
in the tabular section "Goods" of the document "Goods and Services Receipt". We will take the data for filling from the "AccountUchetU" requisite
of the reference book "Nomenclature" of the receiver base.

The situation is complicated by the fact that we will work with tabular part so you need to tweak
rules for converting a group of properties - PKGS... We will need to refer to the current row of the tabular section.

Creating rules for converting a group of 1C properties

We have already developed conversion rules for the document "Goods and Services Receipt".

But for the tabular section "Products" there is no property conversion rules"VAT rates".
You need to add a new rule for converting properties by clicking on the "Synchronize properties ..." button.

The "Configure property conversion rules (Goods / Services Receipt)" dialog will appear.

You need to repeat what has been done in the image and press the "OK" button.

Although we created conversion rule for a group of properties but it's not ready yet.
Remember that the details of the "VAT rates" tabular section differ in the types of values.
In the source database, this variable has the type "ReferenceLink.VAT rates"
and in the base of the receiver - the type "EnumerationLink.VAT rates". We're missing a rule here
converting from a directory to an enumeration.

Event handlers for property group conversion rules

To configure the conversion of a property correctly, you need to create a new rule for converting objects.

In the dialog that appears, we indicate that the "VAT Rates" directory is converted into an enumeration with the same name.

There will be no property conversion rules for this rule.
Therefore, when saving this rule, in the dialog that appears, select "No".

In the dialog with the question "Create rules for uploading data?" also choose "No."

Double-click to open a dialog with setting the object conversion rule (VCO) "VAT rates".
Here, on the “Event handlers” tab, select the “On unloading” event and define the “Source” and
"LinkNode", that is, what will be transferred.

If Source. Rate = 0 Then
LinkNode = "Rate0";
ElseIf Source. Rate = 12 Then
LinkNode = "Rate12";
ElseIf Source. Name = "without VAT" Then
LinkNode = "No VAT";
EndIf;

After writing the handler, click the "OK" button.

In the information on handlers:

Source - Arbitrary - the unloaded source object (link or arbitrary data).
LinkNode is an initialized xml link node. Can be used,
for example, to initialize properties of other objects.

Now we will explicitly indicate the use of this object conversion rule when unloading the VAT rate variable.
Go to the tab "Conversion of properties (*)" of the document "Receipt of goods and services" and open the conversion
group of properties "Products", double-click on the property "VAT rates" and in the dialog that opens, in the field "Rule"
select the rule for converting the object "VAT rate".

Click the "OK" button.

Now it remains for us to set the accounting accounts in accordance with the values ​​that are defined for the item.
Let's go to the "Object conversion rules" tab, find the "Goods / Services Receipt" object and
by double clicking on it, we will open the Object Conversion Rules (OCP) dialog.
Let's go to the “Event handlers” tab on the “After loading” event and write the following:

For each LinePTF From Object. Products Cycle
StringPT. ACCOUNTBU = StringPT. Nomenclature. ACCOUNTU;
End of Cycle;

Now let's load these rules in the source using the external Universal Data Exchange XML processing - V8Exchan82.epf.
Let's upload the data to an xml file. Then, we will open the same processing in the receiver base and select the upload xml file and load the data.

By the way, the processing "Universal data exchange in XML format" can be opened via the menu item
"Service" | "Other data exchanges" | "Universal data exchange in XML format". A little was written about this in a note by Fr.