1s 8 download configuration update. What to pay attention to

The procedure for updating the 1C database requires certain knowledge and skills in handling a computer, so it is often difficult for the user. Therefore, if possible, it is best.

There are several ways to get the files necessary for updating:
- firstly, the latest updates are available on the site users.v8.1c.ru, access to which you get when concluding an agreement for ITS (information technology support);
- secondly, you can update 1C via the Internet, for this you need to have registration data (login and password).

This article describes how to update the configuration when downloading update files, but you can use this article to update the program via the Internet. To do this, skip step 2, and when performing step 4, check the box 9 and uncheck the box 8, and then enter your login and password.

ATTENTION! If your configuration was finalized by 1C programmers, it is not recommended to update on your own, because. this can lead to errors and even loss of data.

This article is an instruction for updating 1C:Enterprise 8.3 configurations. So, let's start in order.

1. First of all, create a copy of your database. you can read about . If you have a backup, in case something goes wrong, you can always return to the starting point and either start the process again or use the services of a 1C programmer.

2. Now we proceed directly to the update. Open the directory with the update, run the setup.exe file and install the update in the default directory.

3. Run the configurator (actions 1 and 2 in the figure). Select a user with administrative rights (step 3 in the figure).

In the Configurator window, go to the menu Configuration → Support → Update configuration(action 4 in the figure).

If step 4 is not available, then you must first open the configuration (step 5) and then repeat step 4.

In the window that opens, select the item "Search for available updates (recommended)" and click the "Next" button (steps 6, 7).

4. In the window that opens for selecting the type of update source, check the boxes as shown in the figure (steps 8 and 9). Click the "Next" button (step 10).

If you update the program via the Internet, then you must uncheck the box 8 and check the box 9.

5. After a short pause, a window of available updates opens. Select the configuration version number and click the "Finish" button (steps 11 and 12 in the figure).

6. Next, the program will ask you questions that you need to answer "Yes", "Accept" and "Continue". When updating the database configuration, a window will be displayed to accept the changes. You must click the "Accept" button (step 13).

7. After that, it remains only to start the regulated data processing in user mode. To do this, close the configurator and run the program in the "Enterprise" mode (ie, as usual). The program needs to run the program under a user with administrative rights.

8. When you start the program, you will be asked a question about the legality of the received update, to which we will answer by performing steps 14 and 15 as in the figure.

9. If the screen displays information about configuration changes, then your configuration has been updated.

Congratulations, you have updated your 1C program!

If for some reason you can’t update the 1C database on your own, then you can leave it and our specialist will do the job!

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

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

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

What to pay attention to

With such a big update (and it doesn’t matter if we do it all manually through the configurator or automatically through the updater), the following points should be taken into account:

  • you need to clearly control the execution, and if on some of the intermediate updates the handlers stopped executing correctly, you need to first execute them error-free and only then continue
  • if the database size and time allow, you need to make backups after each of the intermediate updates (we will discuss them 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 decide to update accounting from version 2.0.12.2), then downloading new updates may not work right away; in this case, you need to download and install updates directly from the 1s website and periodically run the updater, and from a certain point it will start downloading updates on its own
  • if you are updating a clean configuration (that you just created), be sure to run it once in user mode so that the initial initialization and data population is done; otherwise there will be problems with the execution of update handlers

Which platform versions to use for such an update

By default, I recommend using the latest version of the 1C platform - even despite the fact that at the time of the release of many interim updates of this version of the platform there were not yet 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 the 1C platform worked a little 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

Ability to backup in sql format

For server databases, by default, the updater makes backups in the 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 advise you to roll back to dt unload

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

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

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

Then go to the "Archive" tab and check the box "Include SQL backup in the archive":

Fill in the necessary settings if required:

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

How to disable backup before updating

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

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

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

How to disable automatic database recovery in case of an update error

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

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 properties of the database and go to the "Update" tab.

Here, check the box "Do not restore the database on update failure":

How to enable updates "on the forehead, and not on key releases"

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

Here, check the box "Search for updates in the forehead, and 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.

In this case, the overall execution time of operations will be significantly longer (due to an increase in the number of updates), and therefore I advise you to enable this mode only for a few 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 no more than 3 releases at a time" on the same tab:

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

How to enable automatic transition to the next subrevision

By default, the updater updates strictly within .

And rightly so, because different editions (for example, 2.0 and 3.0) differ dramatically and, almost always, the transition between them requires the attention of a specialist after.

But here is the transition between under editions (for example, from version 11.1 to 11.2) is usually not so "terrible" and for some configurations can be considered commonplace.

How to enable intermediate backups

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

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

The presence of 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 options" operation:

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

And click the "Run" button.

How to update the modified database

If you have a modified standard and when you try to update through

  1. Preparing for the update:
    • Download the 1C update distribution kit from the official website;
    • Install the configuration update template;
    • Create an up-to-date backup copy of the infobase.
  2. We update the configuration:
    • Installing the update through the configurator;
    • We start the infobase in user mode.

Preparing to update the 1C configuration

Downloading the 1C update distribution kit

To update the 1C 8.3 configuration, we need an update distribution kit, which can be obtained:

  • on the user support site https://users.v8.1c.ru;
  • on the ITS disk;
  • through a 1C partner in your city.

Before downloading the required distribution kit for updating 1C 8.3, we look at which release of the 1C 8.3 program we currently have installed. Main menu - Help - About :

We go to the official user support website and check the table - to which release you can update our configuration of the 1C 8.3 program:

Very important! Follow this 1C 8.3 update table and install in stages. If you have not updated for a long time, there is a great temptation to immediately install the current release using the full configuration distribution kit - *.cf file. But then there is a high probability that you will miss a release where the developers replaced or removed some objects, and you may lose some data.

For example, if we had release 3.0.43.100 installed, we would first install 3.0.43.148 and then the latest update release, 3.0.43.162.

Attention!!! Don't forget to make backups! After all, if the configuration update fails, you can always restore our database.

Launch the infobase in the configurator:

Main menu - Administration - Upload infobase:

You can read about the methods of backing up the database in 1C 8.3 in the article

We are updating the configuration 1C 8.3

Installing update 1C 8.3 through the configurator

After we:

  1. downloaded and installed the configuration template;
  2. created an up-to-date backup copy of the infobase;

Let's start updating the configuration:

Main menu - Configuration - Support - Update configuration:

If the "Update configuration" button is not active, then you need to open the configuration (metadata tree):

Installing the switch "Select update file" - "Next":

Specify the path of the update file:

We go to the directory where the templates were installed and select the update configuration file 1cv8.cfu:

Button "Ready":

Click on the "Continue Update" button:

The next window will display information about the current and new versions of the 1C 8.3 configuration of the supplier. We agree:

After the 1C 8.3 configuration is updated, we agree to update the database configuration:

We accept changes:

How to update 1C 8.3 through the configurator yourself, see also in our video tutorial:

We launch the 1C 8.3 infobase in user mode

After completion, we launch 1C 8.3 in user mode in order to process the update of the infobase.

You can start in user mode through the 1C launch window or through the configurator:

We confirm the legality of receiving the update 1C 8.3 and click on the "Continue" button:

We are waiting for the completion of the update 1C 8.3:

Now we have updated our 1C 8.3 configuration to the current release:

Attention! If you are installing 1C 8.3 update of several packages, be sure to run IB in user mode after each 1C 8.3 update.

In conclusion of this article, we note the important points:

  • Before updating 1C 8.3, create up-to-date backup copy;
  • Perform the update 1C 8.3 in stages;
  • After each update of 1C 8.3, run the infobase in user mode.

In order to simplify the process of updating the configuration of the 1C 8.3 database, a mechanism is provided that allows you to search and install updates in user mode, that is, without using the Configurator mode. See our video for how to do it.

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

Consider an example of a configuration update Accounting 2.0 with non-standard changes in modules, roles, event subscriptions, exchange plans, etc. The cases discussed here won't be too hard to update, I'll just show you how to update with them so you can figure out your cases.

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

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

  • Download the configuration update file from the site users.v8.1c.ru or get it from any other available sources (for example, from the ITS disk);
  • Unpack and install the 1C 8 update file to any folder on your hard drive;
  • In the folder with the release number 1C 8, find the file 1cv8.cfu - it is this file that contains configuration updates;

  • Run 1C:Enterprise in mode Configurator;
  • Go to menu Configuration -> Support -> Update Configuration.

  • In the opened window "Configuration update" set the flag on the item Selecting an update file and press the button Further(if you want, you can use the first paragraph Search for available updates and search for update files automatically) ;
  • In the "Specify the update file" field, select the .cfu file from the folder with the release number. Note that you can not update the configuration of the 1C 8 base 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 in sequence;
  • In the next window, you will see a description of this update. You can also see which versions of the configuration 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 with a hint about which releases to install;
  • If the selected file is suitable for updating the configuration, a window with information about the version of the update will appear. Click the button to continue updating. OK;
  • After that, the update process will start. If your configuration is typical, then upon its completion, all that remains is to agree to change the current configuration and run 1C 8 in mode Company;
  • If you are updating a configuration with changes (non-standard), then after the update process is completed, a window for comparing and merging the old and new configurations will appear.

Updating a non-standard configuration 1C analysis of an example

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 typical metadata objects (common modules, roles, documents, directories, etc.). It is necessary to make sure that all your changes remain in place, safe and sound, but at the same time, all the changes of the 1C company contained in the update file were also applied. For this, when updating the changed configuration, a comparison window appears. Main Configuration(with your changes) and New provider configuration(updated typical configuration).

This window has two columns, each containing a metadata tree. The first shows the current database configuration metadata, and the second shows the updated vendor configuration metadata (updated generic configuration). Changed objects are marked with green pencils, the typical metadata objects that you modified are marked in the first column, and the typical metadata objects modified by the update are marked in the second. Thus, in order to correctly update a non-standard 1s configuration, you need to find all metadata objects that have been changed by both you and the update (that is, changed twice).

To do this, click the button at the bottom of the window. Filter, set the flag in the opened window 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. are added to your configuration, then updating the configuration will not overwrite them, they will remain in their place and nothing will happen to them. The problem is only modified generic objects.

To properly 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 difficult task and requires maximum care and concentration.

Shared module update.

  • Consider an example: To a common module Version ControlConfiguration you made the following changes:
    • In procedure CheckConfigVersion() commented out the line: //OpenFormModally("CommonForm.DeprecatedConfigurationVersion", Parameters);
    • We added our own procedure to the module with the name MyTestProcedure().

    When updating, this module has changed, 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 get from it. First, we can see that the common module has changed in both the main configuration and the updated vendor configuration, as indicated by the green pencils in both columns. Secondly, in the first column we see a checked box next to the name of the common module, it indicates that the modules will be merged (what we have changed and the standard updated one). Thirdly, in the last column we see in what mode the modules will be combined. In this case, the value is set to: Take from the new provider configuration, this means that our changes will be completely overwritten, and the changes made by the update will be fully applied.

    Other merge modes offer partial merge of modules, with different priorities. But I strongly recommend that you do not use these modes, because after that your module may end up with a natural "porridge": some of your changes will be overwritten, and some typical changes will not be applied. So change the values ​​in the column Merge mode... we never will. Fourth, if you uncheck the checkbox in the first column opposite the module, then the merging will not be performed and the module will remain as it was before the update. Based on the above points, there are two ways to update the common module:

    • Overwrite your changes by setting the default ones. Then manually make the overwritten changes to the updated module;
    • Do not update the module and make typical changes manually.

    Configuration Comparison Mechanisms

    To compare changes in a module, you can use the following built-in mechanisms of the configuration comparison-merge window:

    • View module differences. To do this, in the comparison window, right-click on the module, select the item Show Differences in Modules… After that, a module comparison window will open, in which you can see exactly which procedures differ in the module that you updated and changed. The upper part of the screen is divided into two columns: on the left is a list of procedures for the main configuration that have been changed, and on the right is a similar list of procedures for the updated typical 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 typical 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 select item In the window that opens, in the area Format, set the flag Detailed. In the report that opens, you can see which lines of the module have 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). Two of its modifications are much more interesting: O report on comparison of objects of the main configuration with the old configuration of the supplier(only changes made by you are visible in this report) and (only only the changes made to the module by the update are visible in this report).



      With the help of 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 differences in modules. In the second report, you can see in how many places a typical update has made its changes.

    We have sorted out all the tools needed to update the module. In order to show their practical application, let's take a step-by-step process of updating the module. Version ControlConfiguration with the above changes. Let's update the module in two ways:

    • Let's update the module, overwriting the changes made to it. We will enter them manually after the update;
    • We will not update the module. Changes received in the update will be made 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 a lot of 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 the 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 like this: 1. Common modules 1.1 Version ControlConfiguration
      • Let's find a common module Version ControlConfiguration Module. Right-click on it and select O from the context menu Report on comparison of objects of the main configuration with the old one. In the window that opens, set the flag Detailed. Also I set the flag Output to text document, because it is more convenient to watch the changes, but this is already 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 numbers of the lines 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 vendor configuration;
        • A procedure has been added, in the old configuration of the supplier it is empty in its place, but in the main configuration it is. We do not 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 select the item in the context menu Show Differences in Modules… Since the line numbers (global numbering) are not visible in the module comparison window, in order to find the first change, we 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 are looking for the text highlighted in red. The changed line can be found in the CheckConfigVersion() procedure.

      • Let's open the text document created to record the changes. In paragraph "1.1.1" we write down the name of the procedure in which the change is located. After that, 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. The following record will be obtained: 1. Common modules 1.1 ConfigurationVersion Control 1.1.1 CheckConfigVersion //OpenFormModally("CommonForm.DeprecatedConfigurationVersion", 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's an added new procedure. Since this procedure is completely absent in the old vendor configuration, its text will be highlighted in blue:

      • Let's reopen the text document created to record the changes. In paragraph "1.1.2" we write 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, which means that this module should be updated, overwriting all the changes made;
      • Next, you need to write changes to other twice changed metadata objects into a text document. But since in this example we are considering a specific common module, we will skip this step;
      • After the work on the twice modified objects is completed, in the comparison / merging window, press the button Run;
      • If a window appears with the text "There are objects changed in the main configuration ...", press the button Yes;

      • In the next window Setting support rules, do not change any settings, but simply click the button Yes;

      • The last message to appear is: "Configuration merging complete." Click the button OK;
      • Save the configuration using the menu File -> Save, pictograms Save(blue floppy disk) or keyboard shortcuts ctrl+s;
      • After the configuration is saved, restore the overwritten module changes. Find and open the module in the metadata tree Version Control Configuration;
      • Let's open a text document in which changes have been made to this module;
      • Paragraph "1.1.1" specifies the procedure CheckConfigVersion, find it in the module and open it;
      • The text document indicates that the line should be commented out: OpenFormModally("CommonForm.DeprecatedConfigurationVersion", Parameters);

        Find it in the module and set the comment;

      • Paragraph "1.1.2" specifies the procedure My Test Procedure, 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 in one of the above ways;
      • The configuration update is completed on this, it remains only to update the configuration using the keys F5 or F7 or the corresponding icons, and in the 1C:Enterprise mode, confirm the legality of the update;

    • Second way:
      • The second method completely repeats the first, except that it acts from the opposite. Therefore, I will describe it briefly;
      • We create a text document with the same structure;
      • Let's generate a report Report on comparing objects of the new supplier configuration with the old supplier configuration;
      • Using the generated report and the module comparison window, we write out the changes introduced by the new supplier configuration into a text document;
      • In the window for comparing / merging configurations, we check that next to the module Version ControlConfiguration FLAG OFF. This means that this module will not be updated;
      • Update the configuration, make changes from the text document to the module Version Control Config.

Exchange plan update.

Consider an example: as part of an exchange plan ByOrganization you have included the guide External Processing. When updating the non-standard configuration 1c, the composition of this exchange plan has 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.

Consider the steps to update the composition of the exchange plan ByOrganization with the following changes:

  • Add new lines to the text document created when updating the common module: 2. Exchange plans 2.1 By Organization
  • Let's find an exchange plan ByOrganization in the comparison / merge window, expand it to a branch Compound. I note that in the exchange plan, the module can also be changed by you, 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 common module, the composition of the exchange plan can either be updated, then adding your changes manually, or not updated, adding typical changes manually. If there are more of your changes in the composition than typical ones, then it is better to update the second way, if there are fewer, then the first. You can see what changes 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 By Organization;
  • We save the configuration;
  • After the configuration is saved, we will restore the overwritten changes to the exchange plan. Find and open the exchange plan in the metadata tree By Organization;
  • In paragraph "2.1" of the text document, a reference book is indicated External Processing, find it in the metadata tree of the exchange plan composition and set the flag indicating the participation of the directory in the exchange;

  • Save and update the configuration;

Update an event subscription.

Consider an example: to an event subscription source Before Deleting Directory For Exchange By Arranging you have included the guide External Processing. When updating, the composition of the sources has changed, the task is similar to the previous ones - to update the non-standard 1c configuration correctly.

Let's take a look at updating the composition of event subscription sources with the indicated changes step by step:


Updating roles in 1C

Before you start talking about updating roles in 1C 8, I would like to note that it is better not to change the typical roles, there is no need for this, and besides, updating the non-standard 1c configuration is very difficult. If you are finalizing any typical 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 do not do this, then over time it will be very difficult for you to update the typical roles (and in an hour it is impossible), since they change a lot in almost every release and configuration comparison reports may not look very clear.

But still, there are often cases when the role has already been changed, and more than once, but there is no time to figure out why and why. Therefore, consider an example: in a typical role Accountant for reference Tax authorities the rights to read and view have been added, while updating the set of role rights has also been changed.

Consider updating the role step by step:

  • Let's find a role Accountant in the comparison / merge window, expand it to a branch Rights;
  • In this example, there is only one change to the role, but this is usually not the case. Therefore, it is much easier not to update the role, but to make standard changes manually;
  • Let's form Report on comparing objects of the new provider configuration with the old provider configuration. Usually there is a lot of information in it, but not all 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 must be set for it. Therefore, after the update, you can either see their arrangement in the vendor's configuration, or install all available ones.

    • The modified objects look like this: - ***References - ***Tax Authorities - ***Permissions - ***Read - ***Value -->Allowed<--Запрещено - ***Просмотр - ***Значение -->Allowed<--Запрещено

      It details 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 - Regulated Report Statistics Form 11HA

    In this case, you can specify which metadata object it is, but in this case it is already clear that the report;

  • In the compare / merge window, uncheck the box next to the role Accountant;
  • After that, it is necessary to write changes to other twice changed metadata objects into a text document and update (the process is described in detail above);
  • We save the configuration;
  • After the configuration is saved, you need to make typical changes to the role Accountant. Find and open this role in the metadata tree;
  • Paragraph "4.1" of the text document says that an object has been added to the role RegulatedReportStatisticsForm11NA, find it in the role metadata tree, check the boxes on the rights Usage And View;

  • Save and update the configuration.

This article about Updating a non-standard 1C configuration is completed. If after reading you have any 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.

Hello dear blog readers. Today I would like to talk about a topic that is quite simple, but which many accountants using 1c bypass, leaving at the mercy of programmers. This is a 1s database update. Or rather, how to update 1s 8 on your own in an absolutely safe way and not wait for the programmer who serves you to find the time to look.

After the reservation, everything is ready for us to take and update the 1c information base absolutely calmly and safely on our own. As I said, there are two ways to update the configuration:

  • This update 1s through the configurator already familiar to us
  • 1s update via internet.

✅

✅

Perhaps I’ll start with the second option, otherwise I’m afraid the frequent appearance of the word configurator will discourage the desire to learn how to update the program. So, now let's open our base in the Enterprise mode, that is, as you usually do it. Recently (relatively recent) in 1s configurations, a tool has appeared for updating 1s via the Internet. To use this feature, in the menu item, select Tools -> Service -> Configuration Update. This will open the Configuration Update Assistant. Leave the update method selected by default and check the box Always connect to the Internet and skip the assistant. In addition, you can set the “Check for configuration updates via the Internet” setting every time you start the program - this is a very convenient feature, I recommend using it.

Next, click the next button. A window will open that will help us find out if there are any recent updates at the current time. Moreover, if such updates are available, then it will provide an opportunity to get acquainted with what exactly the 1C developers have implemented in the new release - the New button in this version.

What are these animals and where to get them? To begin with, all the updates that 1s releases for their configurations are posted on a website specially created for this users.v8.1c.en.

In the window for connecting to the user site, you just need to enter the user code (login) and the password intended to enter the service users.v8.1c.ru.

OK, you found out your username and password or registered, what's next? Then we enter these secret numbers and letters and the update process begins. Just keep in mind that if the program has not been updated for, say, six months or a year, then this process will take a long time, since the program needs to download a sufficient number of updates from usersv8.1c.ru and then install them. And all this time the program will be unavailable for work. By the way, the duration of updating in this way is its disadvantage. Although installing updates once or twice a month during your lunch break will not be difficult. So we started the update, we see the window:

Then a window will open prompting you to restart the 1s enterprise. There is one more notable feature in this window. By clicking on Create an IB backup, a window will open with a choice of the preferred option. If you didn’t create a backup copy before the update, I recommend that you select Create a backup copy of IB and save it in the specified directory, so you will definitely know where your copy is.

The program will exit and a very nice window will open.

You can go to dinner or watch the news in classmates. By the way, the database backup will be created in the .dt format. Another point that I may have missed, but this is logical in principle, in order to update 1s via the Internet, an Internet connection must be active.

At the end of the lunch (update), you will see that the program has restarted and requires you to confirm the legality of receiving the update, so otherwise 1c will be able to prosecute you J and click continue.

No, that's not all! We have to wait a little more until the updates are finally installed. The program will do everything by itself. Upon completion, a window will open in which you can see the list of updates in each of the installed releases.

How to update 1s through the configurator

✅

✅ CHECK LIST for checking payroll in 1C ZUP 3.1
VIDEO - monthly self-check of accounting:

✅ Payroll in 1C ZUP 3.1
Step by step instructions for beginners:

The second way to update 1s through the configurator is a little more complicated, but it’s also quite easy for a mere mortal to figure it out. So, first you need to find out which release (version) of the configuration we (you) currently have installed. To do this, there is a menu item Help -> About the program. For us, the line with information about the configuration is important. I show on the example of the configuration 1s Salary and personnel management, for other configurations everything is the same.

Next, you need to download the update files to the desired release. Where can you get them? And all from the same resource usersv8.1c.ru, which was discussed above. How to work with this resource and what you can find useful on it, read the article. Now we only need to enter a username and password to enter our personal account: https://login.1c.ru/login. Then go to the software update section https://users.v8.1c.ru/distribution/total and find your configuration. Suppose this is 1s ZUP edition 2.5 and click on the title:

A wonderful page will open where you will see the updates ever released for this 1s zoom. Well, in my example, I need to update the 8.2 zoom from release 2.5.69.3 to the latest available 2.5.78.1.

The file is downloading. Save it, say, in a special folder - updates. For convenience, you can download each file to a separate folder, the name of which is the version of the saved update. This is useful when you need to install a lot of updates. I will do it, this is my case. If you need to install one or two updates, then you can not bother.

✅ Seminar "Life hacks for 1C ZUP 3.1"
Analysis of 15 accounting life hacks in 1s zup 3.1:

✅ CHECK LIST for checking payroll in 1C ZUP 3.1
VIDEO - monthly self-check of accounting:

✅ Payroll in 1C ZUP 3.1
Step by step instructions for beginners:

Then we go into each folder in turn and run the updsetup available there. To run it, you need to have WinRar installed on your computer. Where to download and how to install this dinosaur is easy to find on the Internet. In short, the updsetup file is the archive that you are now unpacking. By running updsetup, a window will open where you need to click the Extract button. As a result, our folder will contain several files, the most necessary of which is setup:

Double-click on Setup and in the windows that open, click Next. Thus, we have installed update 70.1 on our computer. These steps must be repeated for all updates. Physically installed updates are located where it was indicated on the second window during installation. In principle, it is not necessary to know this, but it is very useful for general development.

Everything we have done so far has been a preparatory stage.

Do not be afraid, because we do not have to understand it now.

Click next in the next window. We also leave only the top switch active (as shown in the figure). The path specified under this switch in most cases will coincide with what was specified in the configuration installation window (I paid attention to this a little higher). That is, we installed all the updates in this folder, and now 1s will use them to update the configuration.

In the next window, highlight the maximum available version for updating and click done. We look at the description of the update, if it is very interesting what new 1s has prepared for us and click to continue the update. In the next window, we study from which release to which the update will be and confirm - OK. All updates are gone.

During the update process, the program will ask a question that must be answered - Yes. We are waiting a little more. Another window will open, it deals with the reorganization of information. You just need to click - Accept.

Everything was updated from 2.5.69.3 to 2.5.70.1. Further, using the same algorithm (from the menu item Configuration -> Support -> Update configuration), we update to the desired release. In my case, up to 2.5.78.1. At the end of the update, the first time you start the program, you will be asked to confirm the legality of receiving the update. Just confirm.

That's all.

To be the first to know about new publications, subscribe to my blog updates: