Changing the configuration 1C 8.3. Personal experience: how quickly and without unnecessary costs update the changed configuration. but. Putting a configuration for support

Software products 1C are specific in the sense that their work is very influenced by the country's legislation in which these programs are used. That is why it is very important to be able to update these products, since in addition to legislative issues, updated configurations will contain correction of critical errors, accelerate all the work of the program and other useful details. There are two options for developing events: the first option is an update of the standard (typical) configuration, which happens quite quickly and does not require special efforts, the second option when you need to update the modified assembly, is more long and complex.

Defining a configuration type

Usually, the user knows exactly what his version has, since the standard assembly is characterized by the lack of interference in the internal objects of the program. Another thing is that programmers are usually modified, respectively, the user comes already a modified product, which he may not guess. There is a simple way to understand whether changes were made there or not. To do this, it will be necessary to enter the configurator mode, the corresponding button of which is in the starting program window. There is a configuration tab, in which there is a support item. After clicking on it, select the support configuration. IN open window There must be an active button "Enable Change Opportunities", also a sign of standard assembly is the presence of the castle icon near the assembly name. These signs indicate that the program modules have not changed, it means that you can perform a centralized update from the official website via the Internet. In the absence of these signs, it can be argued that the programmer worked on the edge of this product, while the situation is possible when the modification was partial, that is, a number of objects were left in its original form. All modified objects remain without identifying pictograms, and standard elements are marked with a yellow cube. Partial modification does not remove the program with support completely, since the ability to update untouched objects will be.

Standard (typical) configuration - preparation for updating

In addition to these problems, it seems to change the legislation or deterioration of the program speed, it is necessary to update it when the 1C program displays the appropriate message. It will be said that this assembly was released for some time ago, now there is an improved configuration, and that it can be updated right now through the site or using an ITS disk. To begin with it is very important to do backup Bases so that you can restore everything, if something goes wrong. This is done three ways. You can simply copy the root folder with the database or flash drive. After starting 1C, the base is selected, and the path to it will be specified in the window. In case of problems, this folder moves to the place of the non-working base. You can act through the configurator, for what you want to select this mode in the program. In the Administration section there is a button to unload the information base. After selecting the folder, the file.dt appears there, which can be opened with the corresponding button in the same section.

The third method takes a little later, at the update stage via the Internet. You can do everything through the ITS disk, which come to the enterprise monthly, also this disc can be taken from an employee who has an agreement with ITS, only one must follow the configuration coincidence. Otherwise, everything is performed via the Internet. There is an important nuance: update packages are installed strictly consistently, and some releases were missed, then the system will need to install them at the beginning. Contained in the Help menu, where you need to press the program section.
If everything is in order with the Internet, then you need to go to the site usersv8.1c.ru, in which the login and password are entered. Next, the desired configurations are selected by reference. The next step is the choice of specific releases, taking into account the very first and those that came out recently. All files in turn are saved on the computer. Before upgrading, you need to open all archive files, and install each release. Releases can be downloaded, as described, and from an ITS disk. Now you need to go to the configurator mode, after which the objects should be displayed, if there are no, then you will need to click the Open Configuration tab.
To update, the user goes to support-support-update configuration. In a new window, search is pressed.

From the proposed options, search is selected in current updates directory, after that the available release is indicated or the one whose name will be allocated fat. All other offers need to be pressed Yes, including the last window for the reorganization of information. The final step is to start the program in the working mode, so that the updates entered into force.

Updating the inepent (modified) configuration 1c

The meaning of updating the changed assembly is that the changes made by programmers are not lost, and changes from the developers entered into force. All listed steps described in the previous instructions are performed and this time, only a comparative table appears on the final step, where the configuration with modified objects will be configuration, and in the second column there will be a list of updates. In these columns there are metadata trees. The program will mark the green marker to which specific objects the programmer makes adjustments, and which caused the changes of the product developers. At this stage, you need to find those objects that are marked in two these columns.

To simplify the search, you can use the Filter button, which is located below, and then mark the option Show the Specified Properties checkbox checkbox. If everything is done correctly, only objects you need in the working window will be displayed. The procedure for updating the non-type modules will not affect the configuration.

You need to analyze this table. In this case, it is clear that the changes occurred in both cases, since there are a pencil icons, since near the name of the module also has a badge, which means that their merger will occur. The last column on the right indicates that when the process is completed, the entire user code will be changed in favor of updating from developers.

There are other modes with a partial association (priority), but these modes are used by experienced users, since the newcomer will turn all the developments in confusing modules. Accordingly, something to change in the last column, no sense. On the other hand, removing the dawn in the first column, the compulsory association can be canceled. Based on this, you can manually make the code into the updated module, or do not touch the code, and manually make the update yourself. To understand what exactly you need to make, you should click on the right mouse button on the selected module and select Show Differences. This step will show differences in specific procedures. At the bottom of the window there is also a division into two columns, but the code itself is already displayed.

Further actions depend on the level of change of modules, if the configuration was rewritten in a dramatic way, then everything will be updated independently, without the help of a programmer, it will be extremely difficult.

Possible when updating 1C

Most errors are allowed when the base is highly modified, as several code pages, all kinds of reference books and other objects, may be confused. It is very important for any changes to create and save the archive for reserve recovery, After that, once again make sure that everything was done correctly. A classic error is to update the inepar assembly, as if it is standard. But even if you follow the instructions described, it is not a fact that the program immediately earns the way it is necessary. Probably without additional setting not enough. The configurator does not displays the changes in the control form controls, respectively, this moment will have to be checked manually, otherwise the update will be shifted. After the update, the configurator can display a ban on the update of the old information base, as document numbers cease to be uniqueThe same applies to records of information.

To solve the problem, it will be necessary:
- change the number of characters in codes;
- change codes in the information base;
- change the property of control of uniqueness in all directories.

In the update process, you can not forget about updates of interfaces and users' rights, which is often overlooked. It has already been described the importance of consistently updating releases, it is also extremely important to apply the built-in configuration update processing, which will allow you to convert the necessary data and fill the base information if necessary. In the interests of the user, monitor the coincidence of the internal identifiers of objects or details, otherwise the update can be lost all operations. Even after thorough preparation of the new configuration, it is impossible to immediately move to combination with the working base used, since it also needs to be updated, after all everything is thoroughly test.

It is necessary to understand that there are options when the configuration will be returned to support, that is, its update process will occur in standard mode For the program, through the release of the release on the Internet. The program is removed from support after introducing modified modules into the product. Removing these modules will return the program in the initial stateBut it is impossible to completely get rid of them, since the normal operation of 1C will be impossible, because for some reason these modules are programmed. Accordingly, these modules can be carried out beyond the program - the work will be performed on external modules, but it will not affect the program. Thus, reference books and other objects will remain on the spot, it is necessary to do this independently without the necessary knowledge problematic, so the return of the program to the standard assembly program, if required, should a programmer.

There are also several tips that facilitate the process of updating software products 1C. First of all, you need to try to modify the program as little as possible, and if only there is no extreme necessity in this, then not to introduce anything third-party there, but to try to solve problems with the typical tools that are in stock. Without eliminating change in the configuration, you need to comment and enter into a separate document so that in the process of restoring anything important was not missed. So that volume software code In typical objects, it was reduced, it should be submitted to its own common module, and it is necessary to understand that the calls for procedures and functions cannot be touched - they must remain in typical objects so that the program can work correctly. In order to optimize, it makes sense to replace all calls for standard procedures and functions that are located in the "self-written" code of objects and in the code external modules, to call procedures from your own module. These procedures are a simple label by which procedures from typical modules will be called. Thus, when comparing the changes, the user will not need to look for the desired lines in the modified code. Update time subject to these recommendations is reduced to several hours of work, and if you leave it, then the process can delay and for several days.

Update the configuration immediately into several releases is very dangerous. The fact is that after each configuration update, the information base update is launched in "1C: Enterprise" mode. Therefore, if you actualize only the last release, information databases may not comply with the latest configuration. In the article, Dmitry Rudakov, Siberian Agrarian Specialist, Siberian Agrarian Group, shares personal experience in one-time configuration update on 12 releases.

Check configuration change mode

Imagine such a situation. The developers of the management of the manufacturing enterprise (hereinafter referred to as the UPP) in release 1 (release numbers here and further were assigned to conditionally) measurement (indicator) of the calculation register prescribed the type "Directory Tower Tower Tower" with the name "Physly". In release 2, they added another dimension - "Employee" with the type "Directory Tower Supplies". When you start "1C: Enterprise", the processing is turned on, which fills the measurement of the "employee", corresponding to the measurement for the "saline" manner. And then in release 3, the "1C" developers removed the measurement of "Physly" and left only the "employee". If you update the configuration from release 1 immediately to release 3, then you can clear the entire calculation register.

And if the configuration is supported with the ability to change, and in the same database is formed regulated reporting, it is necessary to update the configuration for each release, which can be very expensive in man-hours. For example, the update of a strongly modified "UPP" on 1 release may take 30 hours of working time experienced specialist.

Therefore, before you start upgrading, you need to determine: do you work in a typical configuration with the ability to change or in the configuration without the possibility of change? To do this, go to the configurator, where in the Performance menu. Configuration - Support - Adjusting support".

Fig.1. Calling Configuration Support Configuration window

If installed " On support ", then this configuration is typical, and if " Included the ability to change " - The configuration is most likely changed (at least such an opportunity is laid). Third condition - " The configuration is removed from the support. " Different configuration states are shown in Figures 2, 3, 4.

Fig. 2. Typical configuration without change

Fig. 3. Typical configuration with the possibility of change

Fig. 4. Configuration removed from support

Algorithm for updating changed configurations

Recently, in front of me the task of updating the modified configuration "Trade Management", Release 10.3.13.2. The configuration was changed as a result of the combination with the branch solution "Bit: Car service control 8" and was continuously refined for two years. Now the configuration was necessary to update to release 10.3.25.1, that is, on 12 releases. I broke the entire update procedure into several stages.

Stage 1. Evaluation of the cost and timing of the update procedure

Before proceeding to independent work, I decided to get an independent assessment of specialists in this area. The only company that has the ability to update the modified configurations by automated methods, is LLC "1C-Ijtisi". I addressed the specialists of this company with a request to evaluate the cost of updating my configuration. To estimate the time and cost of work, I provided the current configuration in need of updating. A day later I received a letter with a report .

Report on the results of assessing the cost and timing of the configuration update:

Configuration: Trade Management, Edition 10.3
Current configuration version: 10.3.13.2
Update to version: 10.3.25.1
Number of updated modules: 1 847
Number of reference releases: 8

The results of the assessment surprised me, because the company's website was indicated on the action - 1000 rubles. For a renewal of one release. Comment "1C-Izhtishi":

"The cost of updating to each missed release is not higher than 2000 rubles. Now the promotion passes, so the cost does not exceed 1000 rubles. But the final price of the service is determined by the results of the Evaluation of Mainports on the update and may be below 1000 rubles / Release".

I also clarified how the releases required for the update were selected. In response, I received a screenshot on which it was clearly demonstrated (Fig. 5). In the version number column, the configuration version is specified to which you want to update. In the "Update version" column, it is possible to update from which release. As a result of the assessment, the number of necessary updates decreased to 9.

Fig. 5. Select releases that need to be used to correctly update the configuration

After studying the report "1C-Izhtisi", I counted the personal temporal costs for the same amount of work. Each update procedure occupies approximately 6 hours. Consequently, the total time costs are 56 (9x6) working hours, that is, about seven working days. In addition, there is a possibility that after the update some shortcomings will be identified: for example, the user will complain that the changes necessary for it in the configuration is lost, and then time costs will seriously increase. Meanwhile, the specialists of the company "1C-Izhtisi" offer to do the entire amount of work in three or four working days. Therefore, I decided to take advantage of their services.

Now briefly explain what it was changed in the configuration.

Highly modified objects. These are objects in which many typical properties changed. Adjustments are complex. Principles of the object are added to table partDisplaced the form of an object and on the list form. Added details in forms added handlers. Changed a typical mechanism for holding a document or recording a motion set for the register.

Highly modified documents:

• "Order provider";
• "Movement of goods";
• "Requirement-invoice";
• "Receipt of goods and services."

Highly modified registers:

• "Parts of goods in warehouses";
• "Goods in warehouses."

Significantly modified objects.Objects in which the requisites are added, either the form of objects or object modules (as a rule, carrying out the non-type document).

• Document "Cartrol order";
• Register of information "Components of the nomenclature";
• Register of information "Written off goods";
• Common modules.

Slightly modified objects. Objects changed only forms and added details.

Directories:

• "Types of nomenclature";
• "Contractants' contracts";
• "Counterparties";
• "Nomenclature";
• "Types of value of the nomenclature";
• "A number of information registers."

In the section "General" changed subscriptions for events, layouts, roles, common modules. Almost everything was changed with a sectoral solution.

Stage 2. Delete confidential information

Before providing employees "1C-Ijtisi" information base for testing, it needs to delete confidential information. For such cases, the company "1C" recommends using the processing of "change in confidential information", which is not very widely known.

Processing "Changing Confidential Information" is intended for selective changes or cleaning information in the information base. Processing can be used to prepare an information base before transferring to testing where you want to hide (clean, change) some information.

Processing ChangesConfidential INFORMATION.epf is on the ITS disk in the 1cits \\ EXE \\ Extreps \\ Unireps81 \\ UpdatePrivateInformation directory. Also this processing You can download the link: http://its.1c.ru/db/metod81#Content:1644:12.

Naturally, confidential information in each company is different, but I draw your attention to the data that you most likely need to be changed:

• Directories: Individuals, Contact persons, contact persons of counterparties, counterparties, price types.
• Information registers: Passport details of the individual, Phiophyslice.

Your list is likely to be wider, but these are the most common data. Their change is unlikely to affect the ability to test your information base. You can also remove all those objects with a group processing, work with which the serving company is not assumed.

Stage 3. Obtaining update results

Three days later, I was provided with CF files and comprehensive instructions on their installation. CF files are provided for control releases that cannot be used for users, as they are updated only metadata. They are intended only for the correct update to the last version.

According to the results of the work done, I can say that all changes in the configuration were saved, with visual viewing, all objects that have been changed have saved their features and differences from a typical configuration. In the course of operation, none of the users reported that some changes were lost.

As a result of the update, I allocated two small tasks for an independent solution.

First. Due to the fact that the update is carried out using the "Comparison, Combination" mechanism, the database configuration is really updated, and is updated correctly, without technical risks due to the accounting of control releases. However, the supplier configuration is not updated. Of course, a technically competent specialist without any problems will complement this work, however, I asked for "1C-Izhtisi" to send more full instructions on updating. In accordance with it, an update will be able to make even an inexperienced specialist.

Second. As a result of the update, all objects remain on support with the ability to change, which can also be indirect disadvantage. If you need to use these services at the same time, then all objects need to put on support again. Make it with me while only the bust of all metadata objects is obtained. Unfortunately, while this process is performed manually, but in the future and it will be automated.

In addition to the two named tasks, one small defects were discovered, which, in principle, does not affect the quality of the update and is rarely manifested. As a result of updating the line of the source configuration code and the updated visually coincide, but at the end of the rows for some reason spaces are added. This is a disadvantage, as somewhat increases the amount of changed code. And in the case of further manual updates, it would be better not to have such sections of the code. In fig. 6 is an example before the update, and in Fig. 7 - example after updating.

Updating a non-standard platform causes great difficulties. We will look at how to update the inepit configuration 1C and describe the phased solution of emerging difficulties.

As in the inepar configuration 1c, perform an update.

General concepts

When updating (Update, English), the input platform changes always affect the standard configuration elements (Configuration, Eng.) Supplier.

In the database (database) contains up to three types of configurations:

• directly database - logical algorithms work with it;
• working (the so-called basic, configuration) - which we periodically change;
• configuration of the Supplier (configp - based on it is created by the user and the working, and the database configuration.

If the program is discharged from support - it will not be from the supplier. However, then inevitably increasing labor costs for the update. Consider updating the Nepical Configuration 1C. An example will be the OSP platform (manufacturing enterprise management).

Blind

At the first stage, you need to remove the differences between the working and the configurations supplied. This will reduce the evaluation of the revision previously introduced by us. Non-compliance between them occurs when extraneous files were used when updating (not supplied distribution) or update methods differed from standard.

Comparison of versions

We carry out reconciliation of versions (working and delivered) numbers. The first is checked in "Configuration" / "Open" / "Edit" / "Properties". In the section "Development / Version". Second to "Configuration" / "Support" / "Configuring Support" / "Version":

When matching numbers, you can switch to the Get File Getting through the update.

Further steps demonstrate how to bring the supplier working and configuration. In order to support those objects that were removed or were added by the user without support. For this:

Saving configuration (working)

Save the configured to a certain file with the name, for example, work.cf. To do this, select "Configuration" / "Save ...".

Obtaining a supplier file

For configure configure, you need a CF file from the Supplier Distribution (the same version). By default, it will be in C: / Program Files / 1CV81 / TMPLTS. Check the availability of the desired CF file in the template table. What to do if not the right file Required supplier configuration version? Then you need to form an empty database from the old, update it to the required version and then use it.

Getting a file via update

To execute the UPDATE CF file, the configp is selected in the command menu: "Configuration / Support / Update ... / File Select / Ready / Run" (sequentially in pictures):

To solve it, it is necessary to remove the mark on the removal from the object in the Configuration of the supplier. Then, after removal, repeatedly perform a comparison - click the "Update" button in the update window.

Restoring settings

Part of the lost settings is restored by the method of combining with a previously saved file work.cf. To do this, select "Configuration / Compare, merge ... File".

Saving and adjusting

To save the configuration configuration menu item, select "Refresh ... database" to save configuration menu item. Here we celebrate a new problem:

Most likely, the reason for this was that these objects were copied from the configp or they were removed by the supplier, and later new under the same names were added. However, with other identifiers. As a result, the objects of the same name appeared, but with different identification keys.

Roles can be simply removed, since they did not change. The props must be renamed, for example, to custom-made version. And after the update, make values \u200b\u200bfrom renamed to the created one. Another situation when updating. How to deal with forms?

From the figure it is seen that the form cleaner is removed by the supplier, and then added to the same name. You need to mark them both on the update and click "execution."

If the Update is issued a message about the presence of links to deleted objects, then, without closing the form, you need to clean the links to it in the properties of the objects themselves. Here it is in the register properties. Next, in the update form, select the Update option, mark the update now the register properties and re-click "execute".

Saving changes to the working and update of the database configuration: "Configuration / Update ... database". Transferring the value of the details RequerRerv1 to custom-made external processing Mode 1C: Enterprise.

Base preparation

According to the results, we prepare two identical databases. The first (basic) is our desired result. The second (auxiliary) is to fulfill preparatory actions. In the case of a file version, simply copy them to the directory and connect to the IB list, with client-server - make unloading / loading.

Comparison

After opening both databases, the configurator will execute their three-way comparison. We use a new configp file to this file - "Configuration / Support / Refresh ... / File Selecting ... / Finished":

Comparison of the working, old and new configurations The supplier gives us a list of changed objects on the filter "Show twice changed properties". You need to solve the problem first:

At this point, work with the auxiliary database is paused until the end of the entire process, the "Run" button no longer click. Go to work in the main database with the resulting list twice changed objects. Consent with the update will lead to the loss of completion made previously. Therefore, for each of the objects it is required to make a solution - how it will be changed.

Cut preliminary estimate Only to reduce work in the subsequent. If the element changes are more contained in the new configp - we leave the Supplier object. Put a tick. Move changes from the configreen. If the changes of the element is more contained in the working configuration - we leave an instance of the configuration object. Take a tank. Move the changes from the configp. Modules need to be compared to the deplocern. To do this, click the button as in the picture:

We set ticks to specify procedures and replacement or removal functions:

Now you need to duplicate the status of the checkboxes in the auxiliary database. In the main thing - click "Run". By this time, in the basic we receive a practically ready-made configuration.

Subsequent comparisons perform again in the auxiliary database. We find earlier changes to the additional comparison of the old configure from the configuration / compare ... ":

Similarly, you compare the old configp with the new one. If there is no new file, it can now be taken from the main base.

So, twice changed objects are obtained. The main base received almost ready-made configuration. It needs to be dealt with twice with modified elements.

IMPORTANT. When analyzing the user should be interested in not the reasons for making certain changes, but their consequences. That is, the main thing is the need to save the functionality. It may be necessary for this not to transfer changed strings, but complete recycling code for a new config.

To make a decision, it is enough to compare forms, tables, and object modules. Sometimes data in reports are submitted in such a form that does not allow to quickly make a decision. At this step, the loss of improvements occurs if the changes relate to the object details of the compound type.

In the comparative report, differing data is given as a list from which it is not clear what data types are added / removed. If the number of reports of the report reaches two hundred, then the process of "manual" comparison seems to be quite time consuming (about fifty hours).

The decrease in consideration is achieved by using, for example, configuration "Comparison of cells" from the company Inform service. It is available to launch in 1C mode: Enterprise and presents the report of the comparison report in a convenient form. Comparison is carried out by 1C capabilities:

The scheme is simple. The configurator creates a comparative object report. Stored in a file, for example, reporting.mxl. In the 1C dialog: the company it opens and compares compared cells (double-click on the right mouse button on the selected cell tabular document). By clicking "Compare" the result of the comparison is given, while the distinguished positions are highlighted by color.

Further statement of actions looks like this.

1. The following report is saved by the same name.
2. After completing the update and transfer of the refinement of a typical configuration, a syntax control of modules and testing the operation of changed objects is performed.
3. After successful testing, the process can be considered complete. It remains to update printed forms, Reports and processing. In some cases, check out the external forms of reporting.

We work with 1C 7.7

Updating a typical platform to the same usually does not cause difficulties. Just adhere to instructions in the instructions. They are in the Update.txt distribution catalog.

There are also no difficulties if additional accounting elements are added to the platform (directory, constants, selections, reports, registers, calculation magazines, etc.). They will be placed when combining platforms. The added documents will also not contribute disharmony, if there were no changes in the signs for the introduction of such added documents.

It is recommended to perform UPDATE on a high-speed PC with a large RAM volume. With its lack of 1C, it may refuse to work out some of the functions and "hang". Big volume virtual memory This problem does not solve.

Creating an archive copy

For this purpose, you need to use the option: "Administration / Save Data ...". It is convenient to specify the name of the archive, aligning it with the creation date (for example, GHMMDD.zip).

Preparation of catalogs

To work, you will need six configuration files (1cv7.md):

1. "Output" to prepare an update (resulting MD file);
2. "Workstar" to track changes when compared and to transfer settings to typen_2;
3. Typical (old) "Tystar_1". On its basis was previously created working.
4. Types. (former) "Tystar_2". To monitor changes in the company 1C in the new standard version;
5. A type. (new) "typical_1". Firm 1C in the new version;
6. "Typan_2" for complex objects.

And five running configurators (all but "typical_1").

Initially, the catalogs are in pairs of the same:

• "Outdoor" and "workstar";
• "Tystar_1 and Tystar_2";
• "Typical_1" and "typical_2".

Combining elements

First, we perform a comparison between 3 and 2, 4 and 5, 1 and 6. For this, each of the first pairs to select the "Configuration / Union ..." item and specify the 1cv7.md metadata file as a pair. The screen will reflect a form with a tree of changed elements. Next, it is necessary to analyze the results of the pairwise comparison 3 with 2 and 4 s 5. Leave items to unite the elements in the updated platforms (1 and 6), in which there were changes from the company 1C (4 C 5), but were not reflected in 3 and 2. 1 and 4 need to be combined in replacement mode.

Others

This includes the billing plan and user interfaces. If there were changes in the account plan, it needs to be updated in the "Combining Objects" mode, together with Typun_2. After combining the interface, errors are checked: duplication of menu items, duplication of toolbars, set signs for the "Location from a new line" toolbars.

Loading is performed over the network or on the server (preferable). First monopolo provides access to the database. And then the base is loaded through the configurator mode. Before loading and after it, data archiving is executed (as described at the very beginning of the section). Next, you need to follow the instructions of the update.txt file. After the download is completed, all directories, except for the service, can be deleted.

We hope our publication helped you deal with the update of the Nepical Configuration 1C. We looked at it regarding the seventh and eighth versions.

Leave comments, write about your experience in updating 1C.

Leave your name and phone number, the operator will contact you in working time For 2 hours.

Moscow St. Petersburg Samara

Step by step instructions with photos

Many users of type configurations 1C are afraid to make changes and update programs. In many ways, these are justified, since the incorrect update of the inepar configuration 1c may lead to loss of data or loss of executed settings. That is why we made up the most detailed step-by-step instructionsin which we show how to correctly update the inepit configuration 1c.

Attention : Before updating, be sure to back up all information databases. This will allow you to return to the initial state if there are difficulties with the update.

Make a backup of information bases simple enough. To do this, run the 1c program in the configurator mode. In the "Administration" tab, select the "Unload Information Database" function. If you wish, you can additionally save the databases on the disk or removable media.

Step-by-step instructions for updating the Nepical Configuration 1C

1. The first stage fully coincides with the update of the 1C typical configuration. Run the configurator mode, which is available only to users with full access rights. In the Configurator tab, select the "Support" item and click "update the configuration".



2. In the next dialog box, you must install a tick on the item "Search for updates in directories". Click "Next".

Attention: Updates 1C are available only to users of licensed programs "1C: Enterprise", to obtain updates to users of professional versions, it is necessary to further conclude an agreement 1C: ITS (information and technological support). You also need to register on the site technical support users https://users.v8.1c.ru/. Register on the site Users of licensed programs 1C can either independently, using the instructions of the supplied program, or with the help of our managers.





Attention: For many configurations there are several program reactions (for example, Accounting 2.0 and Accounting 3.0). When you select the update, pay attention to which edition will be updated.

3. In the window that appears, check the loyalty of the selected update. If all data is true and you agree with them - click "OK".



4. The update process may take a few minutes. After that, the window appears with the result of a comparison of the new and current configuration so that you see which systems will be updated. Click the "Run" button.



Attention : 1C: Enterprise 8 allows you to automatically update even modified configurations. If a changes made Do not intersect with objects developed by 1C (for example, additional details added in the document or added a new reference book) update will be performed correctly. However, if the settings are "intersect" with typical objects, it is recommended to invite 1C specialist to the update.

5. If you are confident that all changes made to the configuration do not intersect with 1C objects, in the subsequent windows agree with the program.





6. After that, the program will propose to update the database configuration. Agree to the program
   
7. In the process of updating the Nepical Configurations 1C, the structure of the information base is changed. This program informs the user in a separate dialog box. You must accept these changes, so we simply press the "Accept" button.
   

The difficulty of accompanying the Nepical configurations of 1C is that they are individual for each individual organization. That is why the company "1C: Franchisi Victoria" enshrines for each company with the unwitting configuration of programs 1C of a personal specialist who knows the features of program configuration. In addition, our technical support service is always ready to respond to your questions.

Update 1C is performed by pressing the "one" button, the typical configuration itself can download 1C update and install it. From the user you will need to enter only registration data.

What if the configuration is non-type? Or typical, but improvements are completed - a reference book is added, a pair of details, the report?

We will find out the answer to this question today.

What is the inepar configuration 1c

Nepiovaya configuration 1C, this is when:

• The configuration is written from zero by the programmer
• The configuration was typical, but changes added to it.
• Even if one props added.

In order to make any changes to the typical configuration, it is necessary.

When updating 1C of the non-type configuration, removed from the support, 1C will offer "to put an inepit configuration for support" back. Then all changes will be canceled (erased).

In order to update 1C of the non-type (modified) configuration 1C, the changes remained, and the 1C update is used - you can use another update mode 1c.

Let's look at the example of the modified configuration that we want to update. This is a typical configuration of 1C Accounting (left), which made changes (right):

4) in the "Physical Persons" directory, in the form module, the function of the program has added

How will all these changes work at the time of updating 1C of the inepent configuration 1c?

Update 1C while maintaining changes in the non-type configuration 1c

Update 1C configuration is usually distributed as a self-extracting archive. After unpacking, you need to start the installation file to install 1C update to the computer (not in 1C!).

When installing the update, you choose where 1C update will be installed. Usually this . You can install in any other folder on the disk, and 1C indicate where there are.

1c update files may be the following type:

• file with the extension CF - contains a completely new type of configuration
• a file with the CFU extension - contains only changes from the previous version.

Both files are stored in the 1C update directory, in the folder with the name version.

Be careful when using the CFU file - it allows you to update only with!

So, to update 1C, select one of the options for menu items:

• Configuration / Compare Combine with a configuration from a file - for CF files
• Configuration / Support / Update Configuration / Select 1C Update File - for CF or CFU files.

The first thing 1C compares two configurations. The configuration of your database is called "Basic Configuration", and the configuration from the update is "configuration from the file".

1C will display all differences in the form of a familiar tree, where the changes are displayed on the right.

Look - on our example, directories that have been changed or added are highlighted.

Since we update 1C non-type configuration, which has been changed - that is, it was once typical, you must enter some settings.

Click the Setup button. Select "Downloadable Configuration is the descendant of the main" (that is, it is a modified typical).

Tick \u200b\u200b"Allow deleting basic configuration objects" allows you to delete if they are deleted in updating 1C. Since we added details and directories to the configuration, and there are no 1C in the update, then 1C will assume that they are removed in the update. Therefore, you do not need to put this tick.

Consider the differences discovered by the platform carefully.

We will reveal the line of reference nomenclature. In the branch details we see that in the standard configuration there is no props, and we add it. Minus means that it will be deleted.

Since we do not need to remove the props, which we ourselves added, you need to do the following (options):

• In the "Setup" button, do not install the "Allow delete the main configuration objects"
• If the checkbox is still installed, then remove the tick against this props. In the picture, there is no ticks in front of the props, as it is not allowed to delete objects.

Also at the directory the nomenclature has changed the form. 1C saw it and shows us in the list of modified objects the form of the reference book too.

To see what changes are made on the form, you can do the following (options):

• Press the right button first on the form in the left column and select the menu item "Open shape", and then in the right. Visually compare two forms.
• Press the right button on the form and select the menu item "Report Compare Report" (Details, Tabular Document)

A report on the comparison of objects, when comparing forms, shows a lot of differences. This is due to the fact that when we add only one field to form - the set of adjacent elements - indents, bindings, etc. is automatically changed.

In the list of changes we see our changes - change in the inscription and replace the field.

We can agree or refuse to change the form by choosing a tick near her. This entails the following consequences:

a) if we put a tick

• the form will be replaced by a new
• our modifications of typical configuration will be erased
• changes from 1C update will be applied
• next, manually will need to return our changes.

b) if we do not put a tick

• the form will be left old
• our changes remain
• new changes from 1C update do not apply
• next, it will be necessary to add changes from the 1C update.

You can use the third option. Open the branch form until the end and in the "Combination Mode" column select "Combine".

c) if we chose "merge"

• the form will be a new new, in which there will be new changes and old
• our changes remain
• new changes appear
• if any field was removed, and another field was delivered to its place, as a result of the combination at the same place, both fields and the old and new
• there are chances that the form will look fine
• next, manually need to check that no "excesses" did not happen

2) in the "Physical Persons" directory, in the form module, in the reading function () added a line of the program

To see the changes in the module of the form, which found 1C, open the branch of the form to the end, press it with the right button, select the menu item "Show differences in modules".

Changes are shown in the context of each function, but at the same time you can view the viewing mode or select the update 1C of the entire module or refuse it.

Another way is to use the magnifier button in this line.

Then we not only see the changes in the context of each function, but we can choose which function we want to update what function, and what no.

3) in the reference book " Electronic representations.. "Removed several details

1C determined that we removed the details of the typical reference book and invites us to restore them.

The directory, we added, 1C offers to delete. In this case, the same rule applies as in the case of the requisite we added (see earlier).

So, our task is to carefully examine the changes detected by 1C and with the help of ticks agree to them or refuse. After that, press the Run button.

Please note that if you deleted the props as a result of 1C update, then the data that has been made to it are made to it are deleted, which means the re-adding the same requisite will not restore these data.

If there are several related objects in the configuration - for example, props and form; At the same time, you allowed the update of 1C shape, but removed the checkbox from the requisite, then the contradiction comes.

After pressing the Run button, 1C finds such situations and reports from them.

After clicking on the Run button, you still have another opportunity to think.

To confirm the update of 1C - you need to select the menu item Configuration / Update database configuration.

To refuse to update 1C - you need to select the menu item Configuration / Return to the database configuration.

The third option (the sequence of the menu items) is:

• Select File / Save
• Configuration / Save configuration to file
• Configuration / Database Configuration / Back to DB configuration.

Thus, you enload the resulting configuration to the file, and refuse to change. You can analyze the received configuration, make manual edits, and later simply download it using the Configuration menu / download the configuration from the file.