Program 1C:Enterprise 8 ➾ THREE+1 WAYS! Step-by-step detailed update instructions. Recommendations.

This article will help you easily update the standard configuration yourself in three ways:

• download the update distribution from the website,
• update via the website without downloading the distribution kit
• update using ITS disk
• or using the Internet Update Assistant.

Attention! Before updating, always make a backup copy of the current database. Do not update the modified configuration yourself; entrust this task to specialists.

NAVIGATOR BY ARTICLE:

Archival download of the 1C:Enterprise information base 8

To download the information base, you need to run 1C:Enterprise 8 in Configurator mode:

After launching the configurator, select the menu “Administration” - “Upload infobase”:

In the window that appears, indicate the path and name of the file into which you want to upload the infobase, and click “Save”:

• If there is drive D in the system: “D:\Archive\accounting”
• If there is no D drive in the system, it is recommended to save a copy to external media (flash) or to the path: “C:\Archive\accounting”

Recommended file name for saving, in the format: YEAR MONTH DAY HOUR MINUTE.dt For example, if archiving occurs on February 6, 2013, at 15-30, then the file name should be as follows: 2013 02 0615 30.dt

Important! Before unloading, it is necessary to shut down all users in the 1C:Enterprise 8 system.

Before updating the configuration, you need to look at the current release and edition. To do this, in the Configurator, click the button according to the figure:

In the window that opens, we see the configuration and edition in the top line, and the release in parentheses in the bottom line:

METHOD 1: Update using a file downloaded from the site

Next, you need to open an Internet browser / browser (on any computer) and go to the address Update ITS programs This is the official website of 1C:Enterprise 8 for registered users.

In the window that opens, you must enter your username and password (if you do not know this data, ask your manager to resend it to you by email).

If everything is done correctly, a list of updates will open for different configurations in different countries. Find your configuration:

In the window that opens, select the desired release:

Note! If you missed several releases, then you need to update the configuration gradually. For example, your current release is 2.0.8.2. To update it to the latest 2.0.9.2, you must first update the current one to 2.0.8.3., and only then to 2.0.9.2. The "Update Version" column shows what the current release must be for an update.

In the release window that opens, select the “Update distribution” item:

After completing step 1. You can begin preparing the configuration update itself. To do this, you need to unpack the update file on the computer on which you need to update 1C:Enterprise 8. To do this, you need to double-click on it

After this, several files will appear in the folder. You need to run the update installation file:

And "Done":

Now the update template is installed in the local directory, and 1C:Enterprise 8 can see it.

In the window that appears, select the required update and click “Finish”

In the window that appears, click "Continue update"

After this, 1C:Enterprise 8 will offer to update the database configuration. Click "Yes".

For some time, depending on the power of the computer, 1C:Enterprise 8 will freeze, comparing objects. Then in the window that appears, click “Accept”

You can run it in 1C:Enterprise 8 mode and work!

METHOD 2: Updating the configuration directly through the website (without downloading the distribution)

To update, you need to open the following window in configurator mode:

In the window that appears, check the boxes as shown in the picture.

METHOD 3: Update using ITS disk

To update, you must insert the ITS Disk into the CD-ROM, which does not have the inscription “Addendum to the ITS Disk.” The disc will automatically start and in the window that appears, click the “Browse CD” button.

In the window that appears, select the item “Reporting forms, program and configuration releases”

In the window that appears, double-click on “1C:Enterprise 8”

We perform similar actions described above and reach the window in which you need to check the box “Search in current directories for templates and updates”:

We update the configuration in a similar way.

Updating using the Online Update Assistant

Automatic update of standard configuration via the Internet

Here we will consider the method of automatically updating via the Internet the standard configuration of “Accounting 8 for Ukraine”, edition 1.2. The article is also relevant for typical self-supporting and budgetary configurations (see list below).

Important!!! If any changes have been made to the configuration, performing the update according to these instructions may result in the loss of such individual changes.

Updating the configuration via the Internet is performed in the “1C:Enterprise 8” mode, so you must initially launch the program and then select the update assistant.

Update Assistant options for the following configurations:

Name	Path
Configuration
Accounting (BdU), ed. 1.2
Management of a trade enterprise, ed. 1.2	menu “Service” - “Online user support” - “Updating configuration via the Internet”
Trade management, ed. 2.3	menu “Service” - “Updating configuration via the Internet”
Trade management, ed. 3.1	menu “Administration” - “Support and Maintenance” - “Search and install updates”
Manufacturing management, ed. 1.3	menu “Tools” - “Online user support” - “Configuration updates”
Salary and personnel management (ZUP), ed. 2.1	menu “Tools” - “Services” - “Configuration updates”
Managing a small company, ed. 1.6	section “Settings” - “Online user support” - “Search and install updates”
BAS Retail Trade, ed. 1.0
BAS Retail Trade, ed. 2.0	section “Settings and administration” - “Support and maintenance” - “Configuration updates”
Trade for private entrepreneurs (UT for PP), ed. 1.0	menu “Tools” - “Configuration updates”

Important!!! In the file version of system deployment, before starting the update, you must shut down the users connected to the infobase. In the client-server version, active connections are terminated and new connections are blocked automatically.

On the first page of the assistant, you must select the option to receive the update “Custom website on the Internet (recommended)” (Fig. 1).

To automatically check for a configuration update each time you start, you should set the “Check for updates at startup” flag.

If the flag is set, then when running the configuration, the “Configuration update” form will open only if the versions of the kit and the current configuration differ.

Figure 1 – initial opening of the update assistant

If there is an update available on the user site, the system reports the version number, a brief description, the size of the update and offers to install it (Fig. 2).

Figure 2 – information about available update

The next step appears if the user on whose behalf the configuration was entered has a password set. To continue, you must enter the password for this user and click on the “Next” button (Fig. 3).

Figure 5 – connection to the site

If you use third-party backup tools, you can disable automatic backup creation using the “Backup” link located at the bottom of the assistant page.

For more information on the procedure for creating a backup copy, see the article “Creating a backup copy of an infobase.”

Figure 6 – backup

Note!

When you select the backup option “Create a temporary backup copy of information security,” an archived copy of the data is saved in the directory: \Local Settings\Temp\1Cv8Update. * ** file name "backup"<дата>.dt".

When you click on the “Next” button, the assistant will update the 1C:Enterprise 8 configuration (Fig. 7). The configuration update process may take a long time, depending on the performance of the computer and the size of the information base.

Figure 7 – update process

After completing the configuration update, 1C:Enterprise 8 will be automatically restarted. After this, you need to click the “Finish” button and the system will be ready for further work (Fig. 8).

Figure 8 – completion of update

Copying of material is possible only with reference to the source and indication to the author of the material. Thank you for respecting intellectual property rights. TQM systems

Rating 4.20 out of 5 based on 5 ratings

Update 1C required for the correct operation of accounting and management accounting.

This article will cover:

This article will tell you how to update 1C:Enterprise correctly and without unnecessary hassle. For example, we will consider the configuration “Enterprise Accounting, Edition 3.0”. The principle of updating standard configurations is almost the same for all types of configuration versions.

The article will describe the update process via the Internet and with an existing distribution kit for updating.

Attention: Before starting the update, be sure to make a backup copy of the information database, this will save your data if something goes wrong.

How to determine the version of the 1C configuration?

Before starting the update, you must find out your configuration version; you can do this as follows:

If you do not have the files to update, you can download them on the website https://users.v8.1c.ru/. To do this, you will need an ITS subscription, namely a login and password. If you have the update files, then skip this step and go directly to .

How to download updates for 1C?

1. Launch an Internet browser and go to the site https://users.v8.1c.ru/.
   
   
2. Go to the section on the website Software updates.
   
   
3. Fill in the fields with login and password. Press the button To come in
   
4. The program update page will open; we will be interested in the following information:
   
   
   Name– the name of the configurations, we found it out when we found out the configuration version.
   Current version– the latest working version of the configuration. For correct operation, you will need to update your configuration to this version.
5. In a collumn Name we find our configuration, in my case it is “ Enterprise Accounting, edition 3.0" Follow the link.
   
   
6. In the page that opens you need to find our configuration number ( 3.0.42.63 ) in a collumn Version update.
   
   
7. You need to find the latest update (there may be several) that is available for your configuration, in my case it is version " 3.0.42.91 " and follow the link.
   
   
8. Here you can find all the information on the selected update, but we need the item Update distribution let's cross it.
   
   
9. On the page that opens, click Download distribution. We save the distribution file to a location convenient for you.
   
   
10. Run this file and unpack it into the current folder (you can select any folder, remember it).
    
    

If your configuration has not been updated for a long time, to install the current version of your configuration you will need to download and install several updates.

How to install updates?

To install the update files on your computer, you will need " Update distribution" It looks like this:

For further convenient perception of information on updates, I advise you to name the directories in which you install updates that are intuitive for you. If there are a large number of them, you can easily get confused in them.

How to update 1C?

1. Launch 1C in configurator mode. (to update 1C you will need full rights). When updating, all users must log out of the infobase (You can check this from the configurator, go to Administration -> Active users. Only the current user should be in the list).
   
   
2. If the configuration is closed, you will need to open it to begin the update.
   
   
3. Make sure that your configuration is supported, to do this, go to the menu Configuration -> Support -> Setting up support. In the window that opens, at the top left, there should be a corresponding inscription “ Configuration is being supported».
   
   
   If you do not have this inscription, this means that your configuration may differ from the supplier’s configuration (it was open for modification/change of the standard configuration). The process for updating a modified configuration is different from the process described in this article. I advise you to contact experienced programmers to update a non-standard configuration.
4. To start the update process, go to the menu Configuration -> Support -> Update configuration.
   
   
5. Turn on the switch to " Search for available updates (recommended)" and press the button Further.
   
6. Check the box “Search for updates in directories” and add another directory to the list. You need to add the directory where you installed the files to update. After that, click the button Further.
   
7. A window will open with a selection of available updates. The recommended update will be highlighted in bold text. In my case it's 3.0.42.91 (update). Select it and click Ready.
   
8. A window will open where you can read the description of the update. Pay attention to the version of the platform, it must be no lower than the one you have installed. Press the button Continue update.
   
   
9. A window will open where you can check the version of the current configuration and the version of the configuration that will be after the update. If everything is correct, press the button OK.
   
10. The configuration update process will begin and may take 5 to 10 minutes. It all depends on the type of configuration and on the performance of the computer on which the 1C update is performed.
    
    
11. A window will open confirming the 1C update - we agree.
    
12. Next, a window will open with a list of changes that occurred in the configuration during the update process. Press the button Accept.
    
    
13. After accepting the changes, run the configuration in 1C:Enterprise mode.
    The program may ask you to update the platform to a more recent version. You will learn how to update the platform in the following articles.
    
    
14. Confirm that you received the update legally.
    
    
15. The process of preparing the information base will start; this may take some time (this depends on the number of updates).
    
    
16. Congratulations, this 1C update has been successfully completed!
    
    

Note: If you haven't updated your configuration in a while, you will need to perform these steps several times until you get the latest version.

Video instructions for updating 1C

To save time, you can watch the video instructions for updating 1C.

2018-05-10T12:47:19+00:00

Let's imagine that we are faced with the task of updating a 1C configuration that has not been updated for a very, very long time; dozens of releases have been missed.

They write to me quite often in this regard to clarify whether it will cope and what pitfalls there may be with such a large update.

What to pay attention to

With such a large update (and it doesn’t matter whether we do it all manually through the configurator or automatically through an updater), the following points need to be taken into account:

• you need to clearly control the execution and if during any of the intermediate updates the handlers stop executing correctly, you need to first execute them without errors and only then continue
• if the size of the database and time allow, you need to make backup copies after each of the intermediate updates (they will be discussed below) in order to be able to roll back to any of them at any time
• if you have a very old database (for example, you decided to update your accounting starting from version 2.0.12.2), then downloading new updates may not work immediately; in this case, you need to download and install updates directly from the 1c website and periodically run the updater, and from a certain moment it will start downloading updates itself
• If you are updating a clean configuration (that you just created), be sure to do a one-time run in user mode so that the initial initialization and data population are completed; otherwise there will be problems with executing update handlers

Which platform versions to use for such an update?

By default, I recommend using the latest version of the 1C platform - even though at the time of the release of many intermediate updates this version of the platform did not yet exist and the errors were different.

I advise you to start experimenting with platform versions only at the moment when you really get stuck on one of the intermediate updates and cannot continue, for example, because one of the update handlers is not running, since at the time of writing this the 1C platform worked slightly differently .

In this case, I advise you to take the nearest intermediate copy of the database and use with it the version of the platform that was recommended at the time the problematic update was released.

What to look for in an updater

Possibility of backup in sql format

For server databases, by default the updater makes backup copies in dt format.

And this is not good for several reasons:

• for large databases, uploading to dt takes a lot of time and computer resources
• uploading to dt cannot be considered a full backup; therefore, if during the update process you want to roll back to one of the intermediate copies, I would not recommend rolling back to dt unloading

I will not dwell on why dt cannot be considered a full-fledged database archive (there is information and discussions about this on the Internet). Let me just remind you that 1C also recommends using this format exclusively for moving from the file database to the server database and back.

That is why the updater has the ability to configure the creation of backup copies in sql format directly from the DBMS.

To do this, go to the server database properties in the updater:

Then go to the “Archiving” tab and check the “Include SQL backup in archive” checkbox:

Fill in the necessary settings if required:

I note that for now only MS SQL Server is supported. For PostgreSQL, you will have to create a backup copy manually before updating the database and abandon the idea of ​​​​creating intermediate archives.

How to disable backup creation before updating

By default, the updater is configured to require a backup copy before updating the database.

If you do not need this, go to the database properties and go to the "Update" tab.

Here, check the box "Do not create a backup copy before updating":

How to disable automatic database recovery when an update fails

This item applies only to file databases, since only they are rolled back to their original state by default in the event of a critical error at the time of update.

At the same time, if you have enabled the creation of intermediate backups (more on this below), then the rollback will be made to the nearest copy.

If you need to disable such recovery, go to the database properties and go to the "Update" tab.

Here, check the box "Do not restore the database if an update fails":

How to enable updates “head-on, not based on key releases”

To do this, open the database properties and go to the "Update" tab.

Here, check the box "Search for updates directly, not by key releases":

From now on, the updater will try to apply all released updates to the database, and not just the necessary ones.

At the same time, the overall execution time of operations will significantly increase (due to an increase in the number of updates), and therefore I advise enabling this mode only for several releases in advance, only to solve the problem with handlers.

In order to limit the update cycle, for example, to no more than 3 releases at a time, check the box “Update to no more than 3 releases at a time” on the same tab:

After the situation with the execution of update handlers returns to normal, I recommend clearing both checkboxes and returning to performing operations along the shortest path.

How to enable automatic transition to the next sub-edition

By default, the updater performs updates strictly within .

And this is correct, because different editions (for example, 2.0 and 3.0) differ radically and, almost always, the transition between them requires the attention of a specialist.

But here's the transition between under editions (for example, from version 11.1 to 11.2) is usually not so “scary” and for some configurations it can be considered normal.

How to enable the creation of intermediate backups

As I wrote above, creating intermediate (after each update) backups is advisable when updating a very old configuration.

Since a situation may arise when the problem with the execution of handlers needed to be solved in one of the previous versions of the configuration, but we have already updated after that for several releases and can only roll back to the original state of the database.

Having all intermediate copies of the database solves this problem.

To enable the creation of intermediate copies, run the database update as follows.

From the "More" item, select the "Run update with advanced settings" operation:

In the dialog that opens, check the box "Create a backup copy after each intermediate update"...

And click the "Run" button.

How to update a modified database

If you have a modified standard one and when you try to update via

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 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 Further(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 Company;
• 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 their 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, 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 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 are different 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, let’s 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 provider 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.
    • Version ControlConfiguration 1.1.2 MyTestProcedure Procedure MyTestProcedure() Export //Procedure text EndProcedure
      
    • 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 the work on the 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 If a window appears with the text “There are objects changed in the main configuration...”, click the button;
      
      
    • In the next window, Setting up support rules, do not change any settings, but simply click the button OK;
      
    • The last message to appear is: “Configuration merging complete.” Press the button 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:
    • 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 look at updating the composition of the exchange plan step by step 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.

Almost all clients use 1C, so sometimes you have to deal with this program, I don’t write processing for 1C, but at least you have to deal with updates, and if several releases are missed, then when you try to update 1C to the latest release, the configurator displays a message stating that you need to install previous updates, and these can be 4-7 files. Of course, this article is not about automatic updating via the Internet, but using files, offline.

We will update using the configuration file of the release we need (the latest), file hosting services with these releases can be found on the Internet, excellent support for updates is https://forum.ruboard.ru, there are sections on 1C where you can view the necessary releases.

Preparing 1C update files

If you missed several releases, then in order to update without installing previous “updates”, you need to use a file called setup, for example BP83_2.0.66.45_setup.zip, it weighs several hundred megabytes, save it to disk and unpack it.

We run the setup.exe file, this is an unpacker that will unzip the 1C update files into the folder we specified, after which we don’t need it. We indicate the desired location and remember where we unpacked it

The file we need will be in the unpacked folder and has the extension *.cf, see the screenshot below

The procedure for updating without installing previous 1C releases

Before updating configurations, be sure to back up the database.

Now to update, you need to go to the 1C Configurator

Loading the configuration from a file

If the configuration is not open after starting the configurator, then open it using the corresponding menu item, it is the very first one, highlighted in green on the screenshot. Next, go to the item “Load configuration from file...”

Select our folder with unpacked files

In the next dialogue we answer “Yes”

If the configurator swears and says that “To execute the command you need to unlock all objects,” then you need to “enable the ability to change” in the “support settings”

Now we repeat the steps of loading the file from the configuration, this one.

This method is not suitable for those who update 1C automatically, via the Internet; it is intended for those who update using release files supplied on ITS disks or on file hosting services.

Faced with the fact that the old 1C configuration, which has not been updated for a long time, asks to install previous releases, and there may be more than a dozen of them, I started looking for information on the Internet on this issue, but unfortunately I didn’t find anything, in the end I found the solution myself, I’m posting it on this blog, maybe it will be useful to someone.