Transferring directories between identical configurations 8.3. Very easy to use exchange processing between identical configurations. Uploading data to XML

And we show you how to use it to GREATLY simplify solving your problems.

Today we will look at how to set up and make a simple transfer of directories and initial balances in just 10-15 minutes.

And this is mass and regular task, which is almost inevitable for most new configurations launched.

Therefore, call your colleagues, it will also be very useful for them.

Especially if they have already seen CD 3 and managed to get scared :)

Yes, when you see her for the first time, it’s not clear at all.

But in reality, everything is VERY simple. So simple that you will even be bored later :)

What exactly is in today's videos

These are 4 videos on data exchange via universal EnterpriseData exchange format.

In addition, we will show an example improvements to standard exchange rules in 1C:Data Conversion 3.0

Total duration – 34 minutes. Content:

• Setting up exchange using the example of 1C:Accounting 8 and 1C:ERP
• How to download standard rules and a universal exchange format in Data Conversion 3.0
• Transferring the metadata structure to CD 3.0
• How to perform your first data exchange
• Finalization of the rules conversion
• How to load new rules without changing the configuration ( without removal from support)

note, that when solving this problem, the loading rules change only in the receiving configuration. And the source configuration works according to standard rules.

If a similar problem were solved in Data Conversion 2.0, then changes would have to be made to the rules of both the source and the destination.

These video tutorials are relevant for BSP edition 2.3.2(for any build older than 2.3.2.43).

If you are using an older version of BSP,0, make an “adjustment” for the changed interface and expanded functionality. To do this, repeat the example from the video yourself.

Video 1:
Loading exchange rules between standard configurations into Data Conversion 3.0

In this lesson, we will perform preparatory steps when making changes to the rules of exchange between standard configurations:

• Loading the exchange format structure into the CD (
• Creating a conversion
• Uploading rule files from a standard configuration
• Unloading the exchange manager module

Video 2:
Refinement of exchange rules in CD 3.0

In this lesson we will show how to fill in object details when loading data.

The problem will be solved - when loading objects from the source configuration, set the comment “Loaded from BP 3.0”.

To solve the problem you will need to enter changes in object conversion rules, in the “Before recording received data” event.

The developed rules will be saved as external processing for further use.

Video 3:
Setting up universal exchange between standard configurations

In this tutorial we will show you how to set up new exchange between typical ones.

The settings will be made in the source configuration and then loaded into the destination configuration.

Also in this video we will show how without changing the configuration upload new exchange rules.

Video 4:
Transferring opening balances using exchange rules

In this lesson we will show a typical functionality for transferring initial balances.

P.S.

Yes, exchanges via txt / dbf / ole, etc. have the right to exist. In some special cases, such as connecting to a web server or transferring an external application from a ready-made format.

However, for standard exchanges – standard methods both faster and much simpler.

And if someone reinvents the wheel, when there is a ready-made universal solution - it’s like writing on your forehead “I don’t know the instrument, I don’t want to study it, I’ll build crutches for your money” .

P.P.S.

We want to show that Data Conversion 3.0 is not difficult.

Unusual - yes. Not everything is immediately clear - yes. There are very ambiguous moments - yes.

But with the help of ready-made instructions and videos, you can master it in literally 1-2 weeks.

Data transfer is a very important process in any accounting system, the 1C 8.3 and 8.2 platform is no exception. Below we will look at instructions on the easiest way to transfer data from one system to another that has a similar configuration (for different configurations, you can use a tool for programmers - or).

Before any action is necessary, the changes are irreversible!

The easiest and most convenient way to transfer data from 1C 8.3 to 1C 8.3 accounting 3.0 is to use processing Uploading and loading data into XML format(download - for 8.2 or for 1C 8.3 or on ITS). The treatment is universal and suitable for any configuration.

Let's not go into details, let's look at step by step instructions on data migration using this processing using the example of the simplest transfer of goods.

Uploading data to XML

First of all, let’s open processing in the source database (from where we will unload goods) and look at the interface:

Get 267 video lessons on 1C for free:

You must immediately fill in the “File name” field - a new data file will be created along this path, which we will upload to the receiver database. Just below, in the tabular section “Data for uploading”, you need to select the data that we want to upload from the database.

After selecting an object from the left table part, you can apply selection in the right table part:

In our example, I want to unload all products with the name “Rake”.

Once all the settings have been completed, the data can be uploaded. To do this, click on the “Upload data” button:

Loading data from xml into 1s 8.3

The data has been unloaded from the source database; now it needs to be transferred to the destination database.

To do this, you need to start processing already in the database into which you need to load the data, and go to the “Download” tab, select the downloaded file on disk and click on the “Load data” button:

This example is only suitable for transferring data between identical configurations on the 1C platform. To understand the exchange mechanism for programmers, we wrote an article -.

This processing allows you to exchange 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)

Operating modes

Processing implements 2 operating modes: Upload (creating an upload file of user-specified data) and Load (reading an upload file created by the mode of the same name and writing the data contained in it). The mode is set by selecting it in the Mode field.

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

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

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

Conditions for the applicability of processing

Processing can only be used in cases where the information base in which the data was uploaded and the one in which the data was loaded are homogeneous (the configurations are identical, the data may differ), or all the uploaded objects are almost completely identical in composition and types of details and table parts, properties of the “leading” metadata object, etc. It should be noted that, due to these limitations, processing is mainly intended for exchange between homogeneous IS.

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

Determining the composition of the unloading

Processing allows for 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 that displays metadata objects for which data can be uploaded. An additional column of checkboxes, "If necessary", sets the need to unload objects of this type"link". That is, if the checkbox is checked only in the “If necessary” column, then the data for such an object will not be downloaded completely, but only to the extent that is necessary to maintain referential integrity in the infobase that will load the download file.

When opening a form, processing sets the sign of unloading by reference to all objects, which guarantees the referential integrity of the unloaded fragment of the information base.

When you click on the “Detect objects that are unloaded by link” button, processing analyzes what data links may be contained in objects that have the full unload attribute set, and automatically fills in the column of flags indicating the need to unload by link. If the object already has the full unload flag set, then the unload by reference flag is not set.

Possible applications

The use of this processing is possible, for example, to create complete or partial backup copy data, exchanging data between information bases, and also as an auxiliary tool in restoring problematic information bases.

When maintaining several working 1C databases, sometimes there is a need to exchange data between them. There are 2 ways to transfer data:

Data transfer using the exchange and processing rules “XML Data Exchange”. Exchange rules are created using the 1C:Data Conversion configuration.

Transferring data between similar infobases using the “Upload and Load” processing XML data».
Let's consider the second option, i.e. uploading and loading data from/to configurations that contain the same (identical) objects we need. To do this, we will use the external processing “Uploading and loading XML data”, which can be downloaded here.

The condition for using this processing is as follows: The information base from which data is downloaded must contain the same objects and with the same details (name and data type) as in the database into which the data is loaded.

Let's consider an example with data transfer using this processing. Suppose you need to transfer the documents “Incoming payment order” and “Outgoing payment order”. The solution to this problem will be as follows.

We open the external processing “Uploading and loading XML data” through the main menu: File? Open... On the “Upload” tab we specify the XML file into which we will save the data.

Then you need to specify the period for which we will unload data objects from the 1C database and the objects themselves. We mark the documents we need for uploading with a tick in the configuration object structure field in the “Data for uploading” column. If the uploaded documents contain links to directory elements that are not in another configuration, then it makes sense to check the boxes in the “If necessary” column so that these elements are also uploaded along with the documents.

Now at this step you need to decide whether to upload their movements along the registers along with the documents or transfer these documents to another database? To re-post uploaded documents in another database, you can use the “Group processing of directories and documents” processing. If the algorithms carried out in the data information databases differ in some way, then the checkbox next to “Upload all its movements with the document” should not be checked.

That's all, the upload setup is complete, everything is simple here! Click the “Upload data” button and wait until the data is saved to an XML file. For more complex unloadings, you can specify selection for unloaded objects not only by period.

After unloading, go to the second 1C database and open the same processing there. Go to the “Download” tab and indicate here the same XML file into which we uploaded the data.

On this tab, check the box next to “Continue loading objects if an error occurs” and click on the “Load data” button. We do not consider other functions, for example, the use of totals, although this function can significantly speed up the loading of objects (records by registers).

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

Transfers data from one 1C database to another via xml file or com connection.

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

On the "Upload" tab there is a flag "Unload directories from documents". When uploading documents with the flag set, directories contained in the document details and tabular parts together with their parents and owners (if necessary).

It can work in two modes: via xml (run one by one in the source database, then in the destination database), via com connection (run only in the source database).

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

Even if the user does not take special actions to save the settings, the processing itself saves the data set in the dataXML.ini file. It stores: “Type of exchange”, “Download directories from documents” and connection parameters for com connections.

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

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 to be transferred using the checkboxes (on any tabs)
• Click "Upload"
• Run the same processing in the database that receives the data. Select the type of exchange “Via XML”.
• Click "Download". The downloaded data will be displayed in a list, from where you can open it with a mouse click. The "Load Test" button on the "Load" tab loads data without writing to the database and displays the downloaded 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 to be transferred using the checkboxes (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 directory or document. If the condition is met, the “Selection” tab appears on the “Unloading” tab.

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

2.4.2. Added selection by organization. Set on the "Advanced" tab. The field is saved in the settings. If the selection is full, only those documents are uploaded that have the “Organization” attribute 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 uploading. Designed for preliminary uploading of the result to a list on which you can check boxes on documents, as well as open the document form for viewing. Uploading from this form limits the list of uploaded documents to only those who have the checkbox selected.

2.5.3. I slightly changed the unloading of information registers (not fundamentally), detailed the messages when unloading information registers (deciphered the record selection). I split the problematic line from user its into two (to make the error easier to understand).

Renamed the other two flags (fitted into place). This did not change the essence of the flags; I hope the names are still clear. “Filled only” is a filter for all table parts, leaving for selection only those objects that contain at least one data object. "Documents with directories" - a flag that allows you to upload the directories contained in it along with the documents.

Part of the unloading has been slightly rewritten (slightly optimized).

When unloading directories contained in documents, a message has been added (previously they were unloaded “silently”).

2.5.5. Added user interrupt handling to upload and download.

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

2.7.4. Added new functionality (tab when uploading "According to exchange plan") Allows, if you have an exchange plan "Full", to upload (and download) data that is registered by the exchange plan.

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

2.8.0. The wish of the respectednirbolz, made in the 251st comment, the "Only new" flag was added.

The configuration of the form has been slightly changed, the main flags have been placed on a separate tab, because the place on the form where they were before is gone :)

3.0.1. Added minimal functionality on managed forms. Exchange of directories, registers of information and documents (optional with movements).