Universal data exchange between identical configurations. Very easy to use handling of exchanges between identical configurations

Probably, every 1C specialist was faced with the situation of the need to transfer data from one infobase to another. In the case when the configurations are different, you have to write data conversion rules. These rules are created in the 1C "Data Conversion" configuration.

You can also transfer data using. In many 1C 8.3 configurations there is standard functionality for setting up data synchronization between different configurations and seamless integration with 1C Document Management.

But when data needs to be transferred between absolutely identical configurations, you can simplify your task and take advantage of the standard XML upload and download handling. Please note that this method, as well as data conversion, matches objects with each other by a unique identifier (GUID), and not by name.

You can download this processing on the ITS disk, or follow the links:

It is versatile and suitable for any configuration.

Let's consider an example of unloading the Nomenclature directory from one 1C 8.3 Accounting 3.0 infobase to another. A prerequisite there will be selection by parent (group) "Woodworking".

Unloading data from 1C to XML

Go to the infobase from where the data will be downloaded (source). Be sure to check them, taking into account all possible conditions in order to avoid undesirable consequences.

Open upload and download processing XML data(Ctrl + O).

We are interested in the "Unloading" tab. First of all, specify the name of the file into which the data will be uploaded and the path for saving. In this case, the data is uploaded "To a file on the server".

In the processing header, the period for which the selection will be carried out is configured. Also, for periodic registers you can specify how the selection by period is applied. If it is necessary to unload movements together with documents, the corresponding flag is set. In this case, we are overloading the directory, so there is no need to configure anything in the header.

Let's move on to selecting data for uploading. In the tabular section of the processing form, check the boxes for the configuration objects that you need to transfer.

The column “Unload as needed” means whether it is necessary to reload this object, if it is referenced by an attribute of the directory we are reloading. For example, the position of the item you are reloading has a unit of measure that is not in the receiver base. If the checkbox in the "Unload if necessary" column is set in front of the reference book with units of measurement, a new position will be created. Otherwise, the attribute value will contain the inscription “<Объект не найден>"And its unique identifier.

In a simple case, without sampling, the item reloading setting will look like this.

V this example you need to select only the nomenclature that is located in the "Woodworking" folder.

Similar processing for 8.2 allows you to conveniently set selections for each configuration object. In 8.3, unfortunately, there is no such functionality. One of the ways out in this situation would be to select the necessary positions on the "Additional objects for unloading" tab.

You can add objects here either manually (the "Add" button) or by request ("Add by request ..."). With a large number of them, the second option is preferable.

In this case, the request will be as follows. Fill in the parameters, complete the request by checking the data, and click on the "Select result" button.

After you have specified all the necessary objects and additional elements for uploading, click on the "Upload data" button. They will end up in an XML file, the name and path of which you specified earlier. The results of this operation will be displayed in messages.

In this example, it was necessary to unload only 3 positions, but five were unloaded. This is because the flag was set in the column “Unload if necessary” opposite the “Nomenclature” reference book. Together with the necessary positions, their parents were overloaded.

Loading a reference from XML

After successfully unloading data from the source configuration into an XML file, open the destination database. The structure of objects and their details must match each other. In this case, the transfer is carried out between two typical configurations of 1C: Accounting 3.0.

Open the processing in the receiver base. This processing used for both uploading and downloading data. Go to the Upload tab and specify the path to the XML file into which the data was previously uploaded. After that, click on the "Download data" button.

The download result will be displayed in messages. In our case, everything went well.

Directory "Nomenclature" in the base - the receiver was not filled. Now it has five elements: three nomenclature items and two groups.

The transfer of various data is a very significant action in any accounting system on the 1C platform. Before exporting a reference book to another database, you need to do backup because the changes made are considered irreversible.

The most popular and at the same time quite simple way of transferring a reference book to 1C 8.3 is to process information data in XML form.

To complete this task, you will need to use the upload / download processing file for 8.2 or for 1C 8.3. This method is universal and the most optimal, it is suitable for almost any installed configuration.

Uploading data

To do this, you first need to go to the program interface and perform a number of actions:

1. Fill in the "File name" field. Using this path, an information data file will subsequently be created for loading into the database.

2. In the area of tables "Data for uploading" select the information from the reference book that you want to upload from the existing database.

3. After that, when the necessary objects are selected, make an overlay selection in the right part of the tables.

4. After completing the installation of all the required settings, export the directory.

Loading data into a directory

To transfer directories to 1C, you will need to perform a number of actions:

1. Start processing in the database where you want to load the information data, and use the "Loading" tab.

2. Then select the previously uploaded file and use the Load Data command.

After performing this action, the migration of the reference book from one database to another is considered to be completely completed.

Very easy to use processing for fast transfer data between identical configurations. Works through xml file or com connection.
Supports regular and managed forms. Works on a web client.

It transfers data from one 1C database to another via xml file or com - connection.

The configurations must be the same (at least in terms of data structure). For example, transfer something from a copy to the working database. The file is created in the processing folder. Transfers directories, documents (along with movements) and information registers at choice. For periodic objects, you can set a period.

On the "Unloading" tab there is a checkbox "Unload directories from documents". When unloading documents with the flag set, the directories contained in the document details and tabular sections are unloaded together with their parents and owners (if necessary).

It can work in two modes: via xml (run in turn in the source database, then in the receiver base), via com - connection (run only in the source database).

In the mode of operation via com, the connection saves the settings for connecting to the server in the dataXML.ini file, the login and password are encrypted, the rest of the data is in the open.

Even if the user does not take any special steps to save the settings, the processing itself saves the data set in the dataXML.ini file. It stores: "Exchange type", "Unload directories from documents" and connection parameters for com - connection.

If the exchange works in XML mode, the upload is made to the same directory from which processing was started. The file "dataXML.xml" is created. It is also loaded from it.

Usage (via xml):

Start processing in the database - the data source. go to the "Upload" tab. If necessary, you can use the "filter by filled objects" flag - it will remove objects that do not contain data from the list fields, leaving only those with at least one record. Select objects for transfer (on any tabs)
Click "Upload"
Start the same processing in the database - the recipient of the data. Select the exchange type "Via XML".
Click "Download". The downloaded data will be displayed in the list, from where it can be opened with a mouse click. The button "Test loading" on the "Loading" tab makes loading data without writing to the database, displaying the loaded data (if it is very scary to load).

Usage (via com):

Start processing in the source database.
Configure (restore settings) for the connection.
Go to the "Upload" tab. If necessary, you can use the "filter by filled objects" flag - it will remove objects that do not contain data from the list fields, leaving only those with at least one record. Select objects for transfer (on any tabs)
Click "Upload"

Updates:

2.4. Added selection by any object data when unloading. Selection is available only when uploading one type of reference or document. If the condition is met, the "Selection" tab appears on the "Unloading" tab.

Added the "file" field, available only when exchanging via xml. "DataXML.xml" is filled in by default. This field is also added to the fields saved in the "dataXML.ini" file.

2.4.2. Added selection by organization. Installed on the "Advanced" tab. The field is saved in the settings. If the selection is filled, only those documents are uploaded where the "Organization" variable is present and the Organization of the document is equal to the selection.

2.5. On the "Upload" tab, the "Upload to list" button has been added. Becomes available if at least one type of document is selected for unloading. It is intended for preliminary export of the result to the list, where you can set the checkboxes on the documents, as well as open the document form for viewing. Uploading from this form restricts the list of uploaded documents only to those who have a mark (checkbox).

2.5.3. Slightly changed the unloading of information registers (not fundamentally), detailed messages when unloading information registers (deciphered the selection of a record). Split the problem line from the user its into two (to make it easier to understand the error).

Renamed two other flags (fit in place). This has not changed the essence of the flags, I hope the names are still clear. "Filled only" - a filter for all tabular sections, leaving for selection only those objects that contain at least one data object. "Documents with directories" - a flag that allows unloading directories contained in it together with documents.

The unloading part was not fundamentally rewritten (slightly optimized).

When unloading directories contained in documents, a message was added (earlier they were unloaded "blindly").

2.5.5. Added handling of user interruption in upload and download.

2.5.6. Fixed a bug with the types of information registers. The registers subordinate to the registrar have been removed from the "Information registers" field. If necessary, transfer them, transfer recorders with movements.

2.7.4. Added new functionality (tab when unloading "By exchange plan") Allows, if there is a "Full" exchange plan, to unload (and load) the data registered by the exchange plan.

Many different little things have been improved to improve the usability of processing. Fixed errors when saving settings.

2.8.0. The wish of the dearnirbolz, made in the 251st comment, added the "New only" flag.

The configuration of the form has been slightly changed, the main flags have been moved to a separate tab, since the place on the form, where they were before, is over :)

3.0.1. Added minimal functionality to managed forms... Exchange of reference books, registers of information and documents (optional with movements).

This processing allows the exchange of data between the same (identical) configurations on the 1C 8.3 platform - Bukh 3.0, ZUP 3.0, UT 11, UPP 2.0 and others, the main thing is that the configurations are the same!

Screenshots

(foto)
(foto)

Modes of operation

Processing implements 2 modes of operation: Unloading (creating an unloading file specified by the user) and Loading (reading the unloading file created by the mode of the same name and writing the data available in it). The mode is set by selecting in the Mode field.

Before starting this or that mode (pressing the Run button), you need to specify the name of the upload file either by entering it manually in the "File name" field, or by using the button for selecting this field and the standard file selection dialog.

In the download mode, it is possible to edit the use of totals when writing registers, which may affect the download speed.

The buttons "Disable totals" and "Include totals" are available when the checkbox "Enable the ability to edit the use of totals during data loading" is checked and are used to manually control the mode of using totals when loading data.

Conditions of applicability of processing

Processing can be used only in cases where the infobase in which the data was downloaded and the one in which the data is loaded are homogeneous (configurations are identical, data may differ), or all unloaded objects are almost completely identical in composition and types of attributes and tabular sections, properties of the "host" metadata object, and so on. It should be noted that, due to the specified limitations, processing is mainly intended for exchange between homogeneous information security.

The format of the upload file differs from the format of the file created when uploading according to the exchange plan by the header part. To unload data (elements of directories, sets of register records, etc.), processing uses the same XML serialization mechanism as unloading according to exchange plans; in this part, the file formats are identical.

Determination of the composition of the unloading

Processing allows both full and partial uploading of infobase data to a file. The composition of the uploaded data is configured in the dialog by checking the boxes in the column of the tree displaying the metadata objects, the data on which can be uploaded. An additional column of flags, "If necessary", sets the need to unload objects of this type"link". That is, if the checkbox is selected only in the "If necessary" column, then the data for such an object will not be completely unloaded, but only to the extent necessary to maintain referential integrity in the infobase that will load the unloading file.

When the form is opened, processing sets the sign of unloading by reference to all objects, which guarantees the referential integrity of the unloaded infobase fragment.

When you click on the "Define objects to be uploaded by link" button, the processing analyzes the links to which data can be contained in the objects that have the complete upload flag set, and automatically fills in the column of flags indicating the need to upload by reference. If the object already has the full unload checkbox selected, then the unload by link checkbox is not set.

Possible applications

The use of this processing is possible, for example, to create a complete or partial backup data, data exchange between information bases as well as how auxiliary tool when restoring problem infobases.

2018-11-15T19: 32: 35 + 00: 00

Universal processing "Upload and download XML data" performs full or partial uploading of infobase data into a file in XML format... Subsequently, this file can be loaded into the infobase using the same processing. The format of the upload file differs from the format of the file created when uploading according to the exchange plan by the header part.

The use of this processing is possible, for example, for creating a full or partial backup of data, for exchanging data between infobases, and also as an auxiliary tool in restoring failed infobases.

Processing supports uploading data with the ability to specify a selection by period. Also, objects are checked for invalid characters when exchanged via XML.

Best regards, (teacher and developer).