2). Updating a standard configuration for several releases at once (8.2) Updating for 1 from 8.2

Home / Doesn't turn on

Very often, various third-party specialists who are not professionally associated with 1C (system administrators, accountants, etc.) ask me for advice on updating 1C configurations. “How to update the 1C configuration”, “How to update 1C through the configurator” - they all ask the same question in different ways. Therefore, I decided to write this article so as not to explain the same thing every time, but to refer them all to it =)
Most modern configurations support automatic updating of the 1C database via the Internet directly from user mode. This is convenient, but has a number of limitations. The main limitation is the Internet. Firstly, it must be, and secondly, it must be fast enough. It doesn't always happen like this. In addition, very often, users forget or are lazy to update configurations, and many missed releases accumulate. As a result, updating them via the Internet can take a long time.
This article will focus on how to update configurations yourself “manually”.

Downloading 1C updates

Let's say you have a 1C: Enterprise Accounting 3.0 configuration, with the following current release

We need to update it to the latest release.
To do this, you need to go to the website https://users.v8.1c.ru/, which is the official 1C website where configuration updates are contained, and click on the “download updates” hyperlink

After this, you enter your username and password, which was created when registering your software product.
And if everything is in order with your ITS subscription and registration (for owners of the basic version, an ITS subscription is not required), then a window similar to this will open:

Where you find your configuration and click the appropriate hyperlink. A table will appear containing all configuration updates up to the latest release.

The current release of our configuration is 3.0.49.20 (see first picture). Here he is fifth from the top on the list.

Those. we have already missed the 4th release: 3.0.49.21, 3.0.49.22, 3.0.49.23, 3.0.49.27.
The hottest heads will rush to download all these releases and update them step by step. But we are lazy people, so let's look at the far right column, which indicates which versions can be updated with the release from the far left column. As you can see, there are a lot of them, and if we look for our current release in the far right column, we will see that it is there for all updates.

Those. we don’t need to download all releases, but just download the latest one, and our current configuration is quite normal to update to it.
After we “fail” into the release link, there will be a window with links to update distributions.

Please note that very often this window indicates the platform release with which your updated configuration will work stably. If the release of your platform is older than this release, then you need to update it.
Download the required distribution to your hard drive.
This distribution will be in the form of a self-extracting archive

Installing the 1C update template

Unpack it, and a list of files will appear in your directory, among which we are only interested in one file, setup.exe

After launching it, the update template installation window will appear.

In this window, you basically don’t need to change anything; click the “Next” button and install the update template.

We update the 1C configuration

After installing the template, you need to open and go to update the configuration in the following path: Menu - Configuration - Support - Update configuration.

Be sure to save your database before updating!

A configuration update window will appear, where you should click all “Next” until you reach the very end.

If you did everything correctly, then your release number, which you downloaded from the site https://users.v8.1c.ru/, will appear in this list of updates.
Select it with the mouse, and the “Done” button will become active

Feel free to press this button, after which information about the update will appear

Click the “Continue update” button. And after some time, a window will appear showing your current release and the release to which your configuration will be updated.

If you see this window, then everything has been done correctly, and you have downloaded the required release to which you can update your configuration. Click “OK” and enjoy the update.
At some point, a window will appear asking you to update the database configuration.

We agree.
In the window where there will be information about data reorganization, click the “Accept” button.

Everything with the configurator! Your configuration has been updated, and to complete the update you need to launch 1C: Enterprise. You can do this through debugging, or you can simply close the configurator and launch 1C: Enterprise in a separate session in user mode.
In user mode, you will need to confirm the legality of the update (for owners of PROF versions), after confirmation the database will be updated.

If everything goes well and no errors occur during the database update process, then you will have a 1C configuration with the new release.

If you missed many releases, you can try updating the 1C configuration using a cf file. How to do this, read my article:

Easy and quick learning of programming in 1C with the help of my books: and

Sometimes it seems that learning the programming language in 1C is difficult and difficult. In fact, programming in 1C is easy. My books will help you quickly and easily master programming in 1C: and “Basics of development in 1C: Taxi”

Learn programming in 1C with the help of my book “Programming in 1C in 11 steps”

No complicated technical terms.
Over 700 pages of practical material.
Each task is accompanied by a drawing (screenshot).
A collection of problems for homework.
The book is written in clear and simple language - for a beginner.

This book is suitable for those who have already started programming and are experiencing certain difficulties with this topic and for those who have been programming for a long time, but have never worked with 1C managed forms.

Without complex technical terms;
More than 600 pages of practical material;
Each example is accompanied by a drawing (screenshot);
The book is sent by email in PDF format. Can be opened on any device!

Promo code for a 15% discount - 48PVXHeYu

If this lesson helped you solve any problem, you liked it or found it useful, then you can support my project by donating any amount:

You can pay manually:

Yandex.Money - 410012882996301
Web Money - R955262494655

Join my groups.

The process of updating the configuration of programs such as 1C can take quite a lot of time, so it is better to turn to professionals for this and undergo 1C training. It is easy to lose concentration at any stage. Which leads to serious errors. Let's look at some of them that are encountered most often. For example, why is 1c not updated?

Description of the simplest options

Most often, the program itself compiles a report, where it writes about why it was not possible to carry out this or that action. For example, the user entered logins and passwords incorrectly when registering. You just need to read the message, follow the links and correct the current situation.

What other errors have become widespread?

The administrator of this program must take care to create an archive before proceeding with any updates. And you need to separately check whether this action was actually completed. The lack of backups is a problem that literally every second user faces. And this is related to the answer to the question why 1s 8.2 is not updated.
Non-standard configurations are often confused with standard ones when updating. Because of this, any changes that were previously made may disappear.
Be sure to familiarize yourself with the history of changes after completing the process. There is a good chance that the configuration will work differently. Or that it will require the use of additional settings to work.
Sometimes the properties of dialog form controls are simply not displayed when working with the program. The reason for this is the carelessness of the user himself. After this, the question becomes even more confusing as to why 1s 8 3 is not updated.
Sometimes after an update the program simply does not allow you to switch to the new configuration. For example, due to the fact that codes and document numbers become non-unique. Errors also appear when updating information registers. In this situation, record sets are no longer unique. Possible solutions include enumerating codes, changing length or content, disabling uniqueness control, changing properties.
Users may not update the database consistently across all releases. And they immediately apply the latest version. This may result in important information simply disappearing from the database. Built-in update processing must be run after each release. Then there is a high probability that the program itself will fill in the empty lines with the information of interest. And it will correct the situation when the 1C release is not updated.
Instant installation on the base after preliminary work is a mistake that almost all users make. But first you need to conduct tests using backup copies. Then there is a greater chance of finding out whether the actions were sufficiently correct.

This article will talk about updating a non-standard 1C configuration (versions 8.2 and 8.3), while saving all the changes made by you (or other developers) to the standard 1C 8 configuration.

Let's look at an example of updating a configuration Accounting 2.0 with non-standard changes in modules, roles, event subscriptions, exchange plans, etc. The cases discussed here will not be too difficult to update; with their help, I will only show the update technique, which will allow you to deal with your cases.

Updating a non-standard 1C configuration step by step instructions

Let's look at the step-by-step algorithm for updating the 1C 8 configuration. This algorithm is universal, its first eleven steps describe the process of updating any standard 1C 8 configuration, and all points together describe updating a non-standard 1C 8 configuration:

Download the configuration update file from the website users.v8.1c.ru or get it from any other available sources (for example, from an ITS disk);
Unpack and install the 1C 8 update file to any folder on your hard drive;
In the folder with the 1C 8 release number, find the file 1cv8.cfu - this is the file that contains configuration updates;
Run 1C:Enterprise in mode Configurator;
Go to menu Configuration -> Support -> Update configuration.
In the “Update configuration” window that opens, set the flag to the item Selecting an update file and press the button Next(if you want, you can use the first point Find available updates and search for update files automatically) ;
In the “Specify update file” field, select the .cfu file from the folder with the release number. Please note that it is not possible to update the 1C 8 database configuration for any release. For each update file there is a list of releases for which it is intended. Therefore, you may have to install several update files sequentially;
In the next window you will see a description of this update. You can also see which configuration versions this file is intended for updating. Click the button Continue update;
If this version of the configuration cannot be updated with the selected file, then you will be given a window prompting you which releases should be installed;
If the selected file is suitable for updating the configuration, a window will appear with information about the update version. To continue updating, click the button OK;
After this, the update process will begin. If your configuration is standard, then upon completion all that remains is to agree to change the current configuration and launch 1C 8 in mode Enterprise;
If you are updating a configuration with changes (non-standard), then after the update process is completed, a window will appear comparing and merging the old and new configuration.

Updating a non-standard configuration 1C example analysis

Let's move on to a detailed analysis of the correct update of a non-standard 1C 8 configuration. The whole problem of updating such a configuration is that third-party changes have been made to standard metadata objects (common modules, roles, documents, directories, etc.). You need to make sure that all your changes remain in place, safe and sound, but at the same time all the changes from 1C contained in the update file are also applied. It is for this purpose that when updating a changed configuration, a comparison window appears Basic configuration(with your changes) and New vendor configuration(updated standard configuration).

This window contains two columns, each of which contains a metadata tree. The first shows the current database configuration metadata, and the second shows the updated vendor configuration metadata (updated typical configuration). Green pencils indicate changed objects, the first column shows the typical metadata objects you changed, and the second column shows the typical metadata objects changed by the update. Thus, in order to correctly update a non-standard 1c configuration, you need to find all metadata objects that were changed by both you and the update (that is, changed twice).

To do this, click the button located at the bottom of the window Filter, in the window that opens, set the flag and press OK.

Now only the objects we need will be visible in the comparison window, which greatly simplifies the update process. It should be noted that if new non-standard documents, directories, roles, modules, etc. have been added to your configuration, then updating the configuration will not overwrite them, they will remain in their place and nothing will happen to them. It is only the modified type objects that are the problem.

To correctly update different metadata objects, you need your own approach, so let’s look at various situations using simple examples. I also note that updating heavily rewritten configurations is a complex task and requires maximum care and concentration.

General module update.

Let's look at an example: To a common module Version ControlConfiguration you made the following changes:
- In procedure CheckConfigurationVersion() commented out the line: //OpenFormModal("GeneralForm.DeprecatedConfigurationVersion", Parameters);
- We added our own procedure to the module with the name MyTestProcedure().
During the update, this module changed; by putting a filter on twice changed in the comparison window, we will see that it is included in the list.

Let's take a closer look at this window and understand what information we can glean from it. First, we see that the common module has changed in both the main configuration and the updated vendor configuration, this is indicated by the green pencils in both columns. Secondly, in the first column we see a checkbox next to the name of the common module; it indicates that the modules will be merged (the one we changed and the standard updated one). Thirdly, in the last column we see in what mode the modules will be merged. In this case the value is set to: Take from the new supplier configuration, this means that our changes will be completely overwritten, and the changes made by the update will be fully applied.

Other merging modes offer partial merging of modules, with different priorities. But I strongly recommend that you do not use these modes, since after doing this your module may end up in a mess: some of your changes will be overwritten, and some standard changes will not be applied. Therefore, change the values in the column Merge mode... we never will. Fourthly, if you uncheck the checkbox in the first column opposite the module, the merge will not be performed and the module will remain in the form in which it was before the update. Based on the above points, there are two ways to update the common module:
- Overwrite your changes by installing standard ones. Then manually make the overwritten changes to the updated module;
- Do not update the module and make standard changes manually.
Mechanisms for comparing configurations

To compare changes in a module, you can use the following built-in mechanisms of the configuration comparison-merging window:
- View module differences. To do this, in the comparison window, right-click on the module and select Show module differences... After this, the module comparison window will open, in which you can see which procedures differ in the updated and modified module. The upper part of the screen is divided into two columns: on the left there is a list of procedures for the main configuration that have been changed, and on the right there is a similar list of procedures for the updated standard configuration. The lower part of the window is also divided into two parts, according to the same principle. It displays the code of the selected procedures. Lines that are present only in the main configuration are highlighted in blue. Lines that are present only in the updated standard configuration are highlighted in green. Lines that are present in both configurations, but do not match, are highlighted in red.
- . You can also use the Object Comparison Report to compare modules. To call it in the comparison window, right-click on the module and select In the window that opens, in the area Format, set the flag Details. In the report that opens, you can see which module lines have been changed and how they look in both configurations.
  
  Despite the fact that this report provides all the information about the changes, it is not convenient to use (at least when updating modules). Much more interesting are its two modifications: O report on comparison of main configuration objects with old vendor configuration(only the changes you made are visible in this report) and (in this report only changes made to the module by the update are visible).
  
  Using the first report, you can see in how many places your changes have been made in the module, this will allow you to quickly find them in the window View module differences. In the second report you can see in how many places the typical update made its changes.
We have sorted out all the tools needed to update the module. In order to show their practical application, we will consider the module update process step by step. Version ControlConfiguration with the changes listed above. Let's update the module in two ways:
- Let's update the module, erasing the changes made to it. We will enter them manually after the update;
- We will not update the module. We will make the changes received in the update later.
First way:
- - Before describing the algorithm, I note that we are considering a very simple update example so that the description does not take up too much space, but the update process in a complex case consists of exactly the same steps, although it requires more concentration and care;
  - Before updating the configuration, let's create a text document. In it we will record changes that will need to be made manually after the update. Data in a text document should be presented in the most understandable way, that is, be structured. In our example we will write this: 1. General modules 1.1 Version ControlConfiguration
  - Let's find a common module Version ControlConfiguration Module. Right-click on it and select O in the context menu A report on comparing objects of the main configuration with the old one. In the window that opens, put a flag Details. Also I set the flag Output to Text Document, because it’s more convenient to see changes, but this is a matter of habit. Let's press the button OK. The report that opens will look like this:
  - The report shows that two changes have been made to the module (before each new change, the line numbers in which it was made are written):
    - Line 34 has been changed, it is commented out in the main configuration, but not in the old supplier configuration;
    - A procedure has been added; in the old supplier configuration its place is empty, but in the main configuration it is there. We don’t close the report, it will be useful to us;
  - Now let's find the first difference in the module comparison window. To do this, right-click on the branch again Module and in the context menu select the item Show module differences... Since line numbers (global numbering) are not visible in the module comparison window, in order to find the first change, let’s scroll through all the procedures in the upper half of the window. We also know from the report that the first change is associated with a line change, so we look for the text highlighted in red. The changed line will be found in the CheckConfigurationVersion() procedure.
  - Let's open the text document created to record changes. In paragraph “1.1.1” we write down the name of the procedure in which the change is located. After this, we need to enter the found change into it so that we can easily find it in the text of the module. To do this, I usually copy into the document not one, but several lines of the procedure at once, before and after the changes. But in this case, the procedure is small and therefore it is enough to copy the changed line itself. You will get the following record: 1. General modules 1.1 ControlVersionConfiguration 1.1.1 CheckVersionConfiguration //OpenFormModal("GeneralForm.Not RecommendedVersionConfiguration", Parameters);
  - Now let's open the configuration comparison report again, look at the next change and also find it in the module comparison window. This time it is a new procedure added. Since this procedure is completely absent in the old supplier configuration, its text will be highlighted in blue:
  - Let's open the text document created to record the changes again. In paragraph “1.1.2” we write down the name of the added procedure. After that, copy the entire text of the added procedure there. 1.1.2 MyTestProcedure Procedure MyTestProcedure() Export //Procedure text EndProcedure
  - Version ControlConfiguration a flag is set indicating that this module should be updated, erasing all changes made;
  - Next, you need to record changes to other twice-changed metadata objects in a text document. But since in this example we are considering a specific general module, we will skip this step;
  - After work on twice changed objects is completed, in the comparison / merging window, click the button Execute;
  - If a window appears with the text “There are objects changed in the main configuration...”, click the button Yes;
  - In the next window, Setting up support rules, do not change any settings, but simply click the button Yes;
  - The last message to appear is: “Configuration merging complete.” Press the button OK;
  - Save the configuration using the menu File -> Save, pictograms Save(blue floppy) or keyboard shortcuts Ctrl+S;
  - After the configuration is saved, we will restore the overwritten changes to the module. Find and open the module in the metadata tree ControlVersionConfiguration;
  - Let's open a text document in which the changes of this module are entered;
  - Paragraph “1.1.1” specifies the procedure CheckConfigurationVersion, let's find it in the module and open it;
  - The text document indicates that the line should be commented out: OpenFormModal("GeneralForm.DeprecatedConfigurationVersion", Parameters);
    Let's find it in the module and set a comment;
  - Paragraph “1.1.2” specifies the procedure MyTestProcedure, which needs to be added to the module. Copy it from a text document and paste it at the end of the module;
  - We save the configuration using one of the above methods;
  - The configuration update is now complete, all that remains is to update the configuration using the keys F5 or F7 or the corresponding icons, and in 1C:Enterprise mode confirm the legality of the update;
- Second way:
  - The second method completely repeats the first, except that it works in reverse. Therefore, I will describe it briefly;
  - We create a text document with the same structure;
  - Let's generate a report Report comparing objects of the new supplier configuration with the old supplier configuration;
  - Using the generated report and the module comparison window, we will write down the changes made by the new supplier configuration into a text document;
  - In the configuration comparison / merging window, check that next to the module Version ControlConfiguration THE FLAG IS REMOVED. This means that this module will not be updated;
  - We update the configuration, make changes from the text document to the module VersionConfiguration

Exchange plan update.

Let's look at an example: as part of an exchange plan By Organization you have included the directory ExternalProcessing. When updating a non-standard 1C configuration, the composition of this exchange plan changed and we are faced with the task of correctly updating the exchange plan, without losing either the standard changes or our own. The tools used to compare changed metadata objects have been described in detail in the previous paragraphs, so for this case everything will be described briefly.

Let's take a step-by-step look at updating the exchange plan By Organization with the following changes:

We will add new lines to the text document created when updating the general module: 2. Exchange plans 2.1 By Organization
Let's find an exchange plan By Organization in the compare/merge window, expand it to a branch Compound. I note that in terms of exchange, you can also change the module; it must be updated according to the rules described for the general module. In this case, we are interested in updating the composition of the exchange plan;
As in the case of the general module, the composition of the exchange plan can either be updated by adding your own changes manually, or not updated by adding standard changes manually. If there are more changes in your composition than standard ones, then it is better to update using the second method; if there are fewer, then the first. You can see what changes there are more using the same reports:
In our example there are more typical changes, so we will write out our changes in a text document: 2. Exchange plans 2.1 By Organization - ***Directories - -->Directory.External Processing
Check that the checkbox next to the exchange plan is checked in the comparison / merging window ByOrganization;
Save the configuration;
After the configuration is saved, we will restore the overwritten changes to the exchange plan. In the metadata tree we will find and open the exchange plan ByOrganization;
In paragraph “2.1” of the text document the reference book is indicated ExternalProcessing, we will find it in the metadata tree of the exchange plan composition and set a flag indicating the participation of the directory in the exchange;
Let's save and update the configuration;

Update event subscription.

Let's look at an example: to an event subscription source Before Deleting the Directory for Exchange within an Organization you have included the directory ExternalProcessing. During the update, the composition of the sources changed, the task is similar to the previous ones - to update the non-standard 1c configuration correctly.

Let's take a step-by-step look at updating the list of event subscription sources with the following changes:

Updating roles in 1C

Before we start talking about updating roles in 1C 8, I would like to note that it is better not to change standard roles, there is no need for this, and besides, updating a non-standard 1C configuration is very difficult. If you are modifying any standard configuration and adding your documents, directories, etc. to it, then create your own role (or several, depending on the situation), in which you include new metadata objects. If you don’t do this, then over time it will be very difficult for you to update standard roles (and sometimes impossible), since in almost every release they change a lot and reports on comparing configurations may not look very clear.

But still, there are often cases when the role has already been changed, and more than once, and there is no time to understand why and why. Therefore, let's look at an example: in a typical role Accountant for reference book Tax Authorities read and view rights were added; during the update, the set of role rights was also changed.

Let's look at updating the role step by step:

Let's find a role Accountant in the compare/merge window, expand it to a branch Rights;
In this example there is only one change in the role, but this is not usually the case. Therefore, it is much easier not to update the role, but to make standard changes manually;
Let's form Report comparing new vendor configuration objects with old vendor configuration. Usually it contains a lot of information, but not all of it is needed for updating:
Either new metadata objects have been added, or rights have been changed for old ones:
- The added objects look like this: - -->
  When adding a new object, the report does not display information about what rights need to be set for it. Therefore, after the update, you can either look at their arrangement in the provider configuration, or install all available ones.
- The changed objects look like this: - ***Directories - ***Tax Authorities - ***Permissions - ***Reading - ***Value -->Allowed<--Запрещено - ***Просмотр - ***Значение -->Allowed<--Запрещено
  At the same time, it is indicated in detail which rights have changed;
In our example, there is only one line of useful information in the comparison report; we add it to the text document: 4. Roles 4.1 Accountant - -->Object - RegulatedReportStatisticsForm11NA
In this case, you can indicate which metadata object it is, but in this case it is already clear that the report;
In the comparison/combination window, uncheck the box next to the role Accountant;
After this, you need to write the changes to the other twice changed metadata objects into a text document and perform an update (the process is described in detail above);
Save the configuration;
After the configuration is saved, you need to make typical changes to the role Accountant. In the metadata tree we will find and open this role;
In paragraph “4.1” of the text document it is said that an object has been added to the role Regulated ReportStatisticsForm 11NA, find it in the role metadata tree, check the permissions Usage And View;
Let's save and update the configuration.

This concludes the article about Updating a non-standard 1C configuration. If after reading you still have questions, feel free to ask them in the comments! At the request of readers, in the next article I can talk about other interesting and complex aspects of updating a non-standard 1C 8 configuration.

Accounting. How to update the 1C: Accounting 8.2 configuration to the latest version

All users of 1C programs know that sometimes the manufacturer releases updates for its software product. Typically, updates are available in the form of cumulative packages, individual configuration files, or downloaded automatically from the 1C website. Despite the fact that the program is mainly carried out by a 1C programmer, the process itself is simple. A trained system administrator, computer scientist and, of course, accountant will be able to produce 1C 8.2 on their own after reading our manual.

First, before updating, be sure to back up your information database. We described how to do this in . Everything that will be said below applies only to a typical configuration. How to determine a typical configuration.

To consider an example of updating the 1C configuration, let’s take 1C: Accounting for Ukraine 8.2 version 1.2.6.5 and update to 1.2.7.4.

Let's open the selected 1C database in configurator mode. In the configurator window that opens, open the configuration by clicking “Configuration”, “Open configuration” in the main menu

If the “Open configuration” menu item is inactive and glows gray, then the configuration is already open, you can skip the previous item. Next, select the menu items “Configuration”, “Support” and “Update configuration” in sequence.

In the “ ” window that opens, leave the radio button in its default position - “Search for available updates (recommended).” Click the “Next” button.

In the next panel of the same window, when choosing further actions, you can do different things. You can select an update from a catalog located on the Internet on the 1C company website, from an update catalog on a CD, from a manually specified catalog, or search through the default catalogs.

We will select the option that allows us to specify the path to the update directory manually. Let's indicate the path here. To select, press the button with the green symbol “+” and then the button with three dots.

Click “OK” and uncheck all other, now unnecessary, update options. So, as shown in the following figure.

Click “Next”. In the next dialog, indicate the required update and click “Finish”. The “Update Description” window will introduce us to the differences between the configurations. If everything suits you, then select “Continue updates”.

Let's wait for the window with information about comparing versions and click "OK" in it.

The update starts; the status bar at the bottom of the window will signal us about the stages of action.

In this state, 1C may freeze and the configurator window may turn white. Other programs may freeze and the computer may generally slow down. There is no need to worry about this case. It depends mainly on the computer's resources. After some time has passed, a message will open, signaling to us that the configuration update has been successfully completed and prompting us to update the database. Naturally, we agree.

This completes the update in Configurator mode for the automatic search option.

*******************************************

If at the stage of selecting an update source we put the radio button in the “Select update file” position, then the update can be performed from a specific configuration file.

After clicking the “Finish” button, the actual update process will begin. At the beginning, a window describing the update procedure opens, click “Continue update”. And the update process will be identical to that described above.