Transfer of directories from 1s. 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 a new exchange between standard 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 are 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.

One of the fundamental elements of any 1C configuration is directories. They store information that is used in most other objects of the 1C application. That is why, when developing or upgrading any system on the 1C platform, new directories are first added and filled out. Every 1C developer should know the basic properties, functions and capabilities of these configuration objects.

Structure and functions of directories in 1C 8.3

The main function of directories is to store and provide regulatory and reference information. Accounting in 1C systems is carried out in the context of directories: Nomenclature, Clients and others.

The developers distinguish a separate type of directories - classifiers. These include information approved, for example, by the state:

• Units;
• Currencies;
• Countries of the world;
• Professions.

By their structure, directories in the 1C program are lists of certain data. To familiarize yourself with existing directories in the 1C configuration, you need to enter it in configurator mode. In the configurator tree, find the “Directory” branch and expand it.

Each of the directories has its own properties set by the developers. Let's look at the main properties using the “Currencies” directory as an example.

The “Basic” tab contains information about the name of the directory and its description. The next section, “Subsystems,” is responsible for including the directory in a specific subsystem.

The Functional Options tab defines functionality using the reference book. The “Hierarchy” tab allows you to create nested directory elements. Hierarchical views of directories can be extremely useful.

On the “Owners” tab, the subordination mechanism is configured. If the directory is subordinate to another, then filling in the “Owner” detail is mandatory.

The “Data” tab determines what information you can add to the 1C directory. At the top you can configure the code and name - one of the standard details, in the center - a list of added details. At the bottom you see the tabular parts of the directory.

The configuration object numbering settings in 1C allow you to create unique numbering for directory elements.

The Forms tab is where developers create interfaces that will be visible to users. The most common forms are Element and List: this is how in the 1C program users see a list of directory data and its elements.

Proper setting of parameters on the “Input Field” tab will create the most convenient working conditions for users. The Quick Select/String Entry/Full Text Search options will help you find the item you need. “Selection history as you enter” will save previously used positions.

The “Commands” section shows a list of existing buttons that call this directory. In “Layouts” you can find all the printable forms of a specific configuration object. “Input based on” will be affected by the developer in cases where it is planned to create other configuration objects based on a directory element.

The “Rights” subsection reflects information about which roles include access to the directory, including filling out directories, changing and reading. “Data Exchange” will inform you which exchange plans the directory participates in. The last tab includes the ability to go into modules for writing procedures and functions. There is also a list of predefined directory values ​​that can be accessed directly in code.

Not all properties are required. Some tabs remain untouched throughout the life of the software on the 1C platform.

To make creating directories in 1C easy, let’s create a new configuration object of this type.

Creating and transferring a directory to 1C 8.3

Using an atypical configuration as an example, we will create and begin to use the “Divisions” directory, which will store data about the structure of the enterprise. In the configurator, in the configuration tree, find “Directories” and click the “Add” button. Fill in the fields:

• Name/Synonym. The first attribute is responsible for the name of the object in the configuration, the second – for the name in enterprise mode;
• The object view is used when opening one directory item;
• List view is used when viewing a list of directory data;
• Explanation – help for users.

Next, we need to add a new directory to one of the subsystems if we want users to be able to see it in the interface. Open the “Subsystems” tab and check the box next to the already existing “General” subsystem.

Our new directory will be hierarchical, since divisions can fit into one another. There are no groups of departments planned at our enterprise, so the “Element Hierarchy” type is selected. We will not limit the nesting of subdivisions.

In addition to the standard set, we will need a few more details and a tabular part for the list of employees. To do this, you need to add them on the “Data” tab in the appropriate sections.

For convenience, you need to add our details to the list form. To do this, on the “Forms” tab, create a new list form and set it as the main one. In the dialog box, check the boxes for all the details that we need. We will also set the shape of the element in order to arrange the details in the order that suits our users.

This completes the creation of the “Divisions” demo directory. We update the configuration and start the system again in enterprise mode. In the “General” subsystem, the “List of departments” function key has appeared. Clicking on it opens the directory list form we have specified with the ability to add elements to it.

Many companies work with several 1C databases, so the developer may be faced with transferring the created directory to another database. For this purpose, along with most configurations, external processing is supplied - “Uploading and loading XML data”. But before you transfer 1C 8.3 directories, you need to prepare a receiving configuration. A similar configuration object with identical fields and table parts should be created in it.

When opening this processing, we need to indicate which objects we want to transfer and select the file. Then the launched download of the directory creates an XML file where it writes all the data.

To load directories into another information base, you need to go into it and open the same external processing. On the second tab, start downloading. This is a manual mechanism, so if you plan to regularly enter new directory elements in one database, then it is better to organize an exchange between databases.

In conclusion, I would like to remind you that creating directories in 1C 8.3 after the system is put into operation will cause problems due to the need for exclusive access to the database. It is safest to update the configuration on the server.

Transferring various data is a very significant action in any accounting system on the 1C platform. Before exporting the directory to another database, it is necessary to make a backup copy, because the changes made are considered irreversible.

The most popular and at the same time fairly simple way to transfer a directory to 1C 8.3 is to process information data in XML form.

To perform 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, suitable for almost any installed configuration.

Uploading data

To do this, you will 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 “Data for downloading” table area, select the information from the directory that you want to download from the existing database.

3. After this, when the necessary objects are selected, apply a selection on the right side of the tables.

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

Loading data into the 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 information data, and use the “Load” tab.

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

After completing this action, migration of the directory from one database to another is considered completely completed.

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 the processing Upload and load data in XML format (download - for 8.2 or for 1C 8.3 or on ITS). The treatment is universal and suitable for any configuration.

We won’t go into details; let’s look at step-by-step instructions for migrating data using this processing using the example of a simple 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 tabular part, you can apply selection in the right tabular 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 -.