1C Combine with the priority of the new supplier configuration. Updating the non-type configuration

1C Nepical Configuration, this is when: 1) 1c configuration is written from zero by the programmer, 2) 1C configuration was typical, but changes added to it, even if one props added.

In this article, we will consider how it is necessary to correctly update the 1C configurations, as well as several techniques for a soft change in typical configurations, i.e. The correct change that will not affect the possibility of further update.

In order to make any changes to the 1C typical configuration, it is necessary to unlock the change in the 1C typical configuration, and in some cases "remove it from support".

In the best update option, the 1C configuration can be updated in fully automatic mode, it is possible when we are prohibited configuration changes. Quite often, it is necessary to include a change in the configuration, since adaptation of applied solutions for the customer's business requirement is necessary, on this option we will stop.

Before updating it is strongly recommended to do backup Databases, you can do it through the Administration menu / unload the information base.

There are 2 update options: a) Update 1C through support (call via the configuration / support / update configuration dialog) and b) through a comparison combination with the configuration from the file. Special attention should be paid that the difference between these two items is that in the first case and the main configuration and configuration of the supplier are updated, and when comparing configurations, only the main configuration is updated, the supplier's configuration remains old. Thus, the most recommended option is to update via update the configuration. To update through configuration support, the supplier delivery files of the CF or CFU supplier are used, which can be found searching in the template directory by specifying the path on the Internet, or directly specify the path to right file On hard disk.

When updating the 1c configuration without the possibility of making a change, the update after selecting the update file occurs in automatic mode if the configuration includes the possibility of making changes, then after selecting the update file, the configuration comparison window will be displayed. In this dialog, we can see how the system offers us to update our inepit configuration 1C. At the bottom of the dialog box, the corresponding legend of object statuses is located: "Object Match Status" indicate the "main configuration" and "new configuration", "statuses on the history of objects" indicate a comparison of configuration objects with the objects of the "old supplier configuration".

Sliding flags next to objects, you can choose, the current configuration object will change, or remain old, as well as the method of changing the object. In the action menu, there is an opportunity to put ticks on subsystems (this is useful if the configuration is on support from several suppliers). Also in this menu, it is possible to specify the priority of combining for all objects to once, by default, the system considers more priority configuration of the supplier. Filter settings allow you to specify which configuration objects we should output for detailed instructions of the combination mode. There are several standard templates Filter, in addition, you can specify filters for each pair of compaable configurations. It is possible to install in the settings "Filter" Tick "Show only twice modified properties", this will allow you to cut out objects, when updating which conflicts did not occur between changes in the supplier and the revisions of these objects:

So, the result will be a list of objects, twice modified when refining a typical configuration and in new configuration Supplier. If you agree with the update, then the revision made in these objects will be lost. Therefore, for each object, it is necessary to make a decision on how it will be updated. At this stage, it is necessary to pre-compare solely in order to reduce the scope of work in the future. The assessment is not accurate fast - "on the eyes." If the changes in the object is larger in the new supplier configuration, then we leave an instance of the supplier object. Leave a tick. Then it will be necessary to transfer changes from the working configuration. If the changes in the object is larger in the working configuration, then we leave an instance of the object of the working configuration. Take a tick. Then it will be necessary to transfer changes from the configuration of the supplier. With modules you can go a little different, because There is an opportunity to compare the modules of the Poprocedure.

Those. If in our configuration 1C and in the configuration of the supplier, various procedures of the module changed, then correctly laying, checkboxes we save ourselves from manual transfer of code changes. To get to it, you must press the button in the form of a magnifying glass next to the name of the module integration mode:

When displaying an action menu by object (for example, by pressing the right mouse button), we can call a report on the comparison of objects.

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.

Several rules that simplify the future update of 1C configurations:

The main rule of 1C update: you need to add new objects, because When updating new objects, the system is not affected

When you change the texts of the modules, it is also desirable to add your new procedures and functions, and from existing to call your new

Using subscriptions to events, due to this you can refine model mechanisms without changing the standard code

Using standard configuration functional

Software creation of form elements (in the Event DepartmentServer)

Thank you!

Licensed policies 1C provides the possibility of making and maintaining refinement in typical configurations, and accordingly, the possibility of their update. *

* Modified or Nepical Configurations 1C is a software product on the 1C: Enterprise platform, which is part of or component automated system The management of the enterprise undergoing a number of changes caused by the needs and specifics of the business, in terms of the forms and composition of reference books, documents, roles, modules, etc., so updating the 1c configuration with change is not at all the same as the update of the typical solution.

Updates manufactured by 1C are aimed at correcting bugs and introducing changes and additions due to legislation. For new configurations recently published, the issue is characterized. large number Updates of the first type. For configurations with a functional, directed, mainly to draw up the regulatory reporting, for example "1C: ZUP", "1C: Accounting", there are more second-type updates.

The specifics of updating the inepar configurations is the need to make all changes in the latest release of 1C, with full preservation of previously produced refinement. This is a non-trivial task, the solution of which does not have a standard scenario, and therefore cannot be fully automated. For this reason, in the method of updating the non-type configurations, manual operations are prevailing, requiring the participation of a specialist.

The steps of implementing the update of non-type configurations are not affected by the amount of refinement. In short, they can be described like this:

• Search and comparison of modified objects;
• Making updates from the new release;
• Introduction of previously made changes, "lured" at the previous stage;
• Check compatibility and processes.

The difference will be in time of implementation: if there are many modifications, the process will occur accordingly more time, will require concentration, attention and manual check.

Consider for the Wednesday of 1C Updating the Nepical Configuration using the example "1C: Trade Management" (release of 2014) to the next available release.

This is a very simple example, but as already mentioned above, the update of a more complex configuration, of course, will require high time and focus on the specialist, but will have the same steps - an update (to a new typical configuration), work with reconciliation made and Imagined changes, etc.

Before updating the configuration, you should unload the information base. This action is recommended to be made before any manipulations with all databases without exception, and especially with non-typis:

Unloading information base Completed:

Please note if the configuration has not been modified, that is, it was typical, then in the configuration window opposite the name, next to the yellow cube, and the icon of the Castle would be displayed:

In the configuration menu, select "Support" and "update the configuration". In fact, at this stage, the actions fully coincide with the standard configuration update process:

Depending on the size of the database and its refinement, the automatic search for available updates may take some time. Therefore, it is worthwhile, despite the recommendations, select the option "Selecting a Update File" and on your own, pre-connecting the archive with updates and saving them, specify the path manually:

Window with reference information, instructions and order of updates:

Configuration comparison window. On the left in the tree displays the state of the available configuration, on the right - information on a new, type version. Also allocated sections undergoing changes. Next, it is necessary to find out which sections were changed from our side and undergo simultaneously changes in the new configuration:

In order to find out what typical metadata objects have been changed earlier and will also be changed when installing a new supplier configuration, you need to select "Show only twice changed properties":

Only objects suitable for this condition remained:

Open the metadata tree, you can see what specific objects will be changed. For more information, click the right-hand key, select the changed object:

You can evaluate changes at the code level using "show differences in modules", but since they must also be remembered to deposit after installing updates, create two reports: "Report on the comparison of the main configuration objects with the old supplier configuration" (existing refinement) and "Report on the comparison of the Supplier's new configuration objects with the old supplier configuration" (updates). *

* Let's figure it out in terminology:

• "Basic Configuration" - the non-type configuration that needs to be updated;
• "Old Supplier Configuration" - a typical configuration from which updates are installed in last time;
• "New Supplier Configuration" is the one to which we update now.

Configure the form of the report and unload it. The list of previously submitted changes is fixed:

After unloading reports, go directly to the update and click "Run". The configurator offers a rule Update "Take from the new Supplier Configuration" (it is indicated in the third column). This means that all improvements will be erased and replaced with typical updated objects. Menuing this rule on a tempting "merge mode" is not worth it, because Automatic association will lead to chaos. Nevertheless, it is better to spend time and make changes manually:

In the window with general information on the removal of configuration with support, you do not need to change anything. Pressing "OK" will result in combining objects. Next, launch the "Enterprise" and write changes to accurately complete the update process:

We accept list of changes: *

* If the "Accept" button is inactive, you should run "Patch Testing":



Run through F5 debugging and get confirmation of the legality of updates:

After the confirmation is received that the process of updates is complete fully completed, you should return to the configurator, go to twice the modified metadata objects and manually make fixed changes at the code level using the unloaded reports. In conclusion, add that after that, it is necessary to check the correctness of the settings and the adequacy of the work processes.

So, we want to make changes to the standard configuration of 1C: company accounting, revision 3.0 (3.0.9.4).

1. We go to the support configuration: Configuration -\u003e Support -\u003e Adjust support;

2. Turn on the ability to change the button of the same name. Agree with the warning of the inability to further automatically update;

3. Configure support rules We leave by default, i.e. "The Supplier's object is not edited" and click OK. Now the ability to change is enabled, but no configuration object is available for editing;

4. If we are going to change, for example, the Document is implemented by the service, in the support configuration we find this document. If you want to add props, you will have to change the rule of support for the object itself. The document is implemented. We change the support rule to "edit with the maintenance of support", while the rules of subordinate objects of the document implementing the services of services (details, table parts, forms, etc.) remain unchanged, i.e. "Not edited." We probably want to place on the form, so we change the support rule for the form of our document to "edit with maintaining support";

5. Now we can add props, place it on the form and change the document module. We add "Mojrevizit", the type of boolean. Next, open the form of the document and drag the "Mojervizit" from the "object" to the form, and add a line to the document module in the "PRIZAP" procedure:

// >>> <<<

Allocate the added rows of the "branded" comment, it will facilitate life there when updating (Ideally describe why all this was done);

6. We update the database configuration so that in the "Enterprise" mode reflected all the refinement. Check in the enterprise mode all that we have done. On the form of the document "Implementation of goods and services", a check box "My props" appeared, and when saving a document, we receive a message about the state of this checkbox.

So we have made simple refinement to a typical configuration.

Now let's try to update our already non-typal configuration, saving all the refined configuration in the updated configuration.

1. Returning the Configuration menu -\u003e Support and select "Update the configuration". Select the update file or trust the platform to find it. Click "Finish" and continue the update;

2. Since we have the ability to change, the update is not in automatic mode, but the comparison mechanism and configuration combined is launched.
By this moment, our database contains three configurations: the main configuration (which we can change), the configuration of the supplier (absolutely typical) and the database configuration. Database configuration in comparison and association is not involved, but two others are involved: "Main configuration", "Supplier Configuration" and the third - "New Supplier Configuration".
So, we have the list of differences in the basic configuration from the new supplier configuration. In this list, the most interesting things are the objects that we have been finalized, and we didn't simply be finalized, but also refined the supplier, they need to leave everything that was done by us, but also bring innovations invented by a typical configuration provider.
We remember that in comparison, three configurations participated (the main, supplier old and new supplier), the platform gives us the opportunity to see those objects that change and we and the supplier.
Apply the filter (click the "Filter" button) and set the checkbox "Show only twice modified properties". We click OK and we see that in a new release, the supplier also made changes to the document implementing the service. We analyze changes in updating. In our case, we can simply set the merger mode for the Module of the Document Module implementing the service and its form: "Combine with the priority of the new supplier configuration". If we left the default mode ("Take from the new Supplier configuration"), then all the refinements made would be lost;

3. Disconnect the filter and make sure that the checkbox from the added "Mojervizite" requisition is removed. Such props in the configuration of the supplier is absent if you deliver the checkbox - will lose props, and with it the data that was stored in it, "Mojrevizit" will be replaced by the "missing requisite";

4. Click "Run". Configure support rules We leave the default and click OK;

5. After the combination process is completed, we are looking for a document implementing the main configuration in the tree of the main configuration. I would make sure that "Mojrevizit" did not disappear anywhere, let's look at the form - and there it is in place, look into the module. In the form of comments, all differences of the unclear configuration module fragments of text are inserted. A double layer is added to the top of each row of the insert fragment of the text, which in the text of the software module makes these rows commented. In addition, to facilitate further work with the resulting text, special lines are inserted into it.

Changed fragments are framed from above and below

// ((MRG [<-> ]

added

// ((MRG [<-- ]

remote

// ((MRG [-\u003e]

In our module, we see that the platform all our works has commented, but at least did not delete:

// ((MRG [<-> ] // // \u003e\u003e\u003e // Report (this information. Everybody); // //<<< //}}MRG[ <-> ]

Remove extra comments:

// \u003e\u003e\u003e Report); one-requisites); //<<<

6. Update the database configuration. Let's look at the result by running the enterprise mode. We see that after the update, all the modifications were preserved and operate as well as before the update, and the release number has changed on 3.0.10.8.

In order to find all changes in the configuration - you need to compare the database configuration (current configuration) with the configuration of the supplier (source configuration without changes). This can be done by the standard features of the platform. In the configurator, proceed to the configuration support settings:

Before, we will open a configuration support window.

By executing the "Compare, combine" command, we will be semi-like list of objects that have been changed in the main configuration compared to the configuration of the supplier. It is such a filter that is enormous for the displayed metadata tree. This may look like a comparison result with the configuration of the supplier.

At this stage, we can view the differences in the objects of the main configuration and configuration of the supplier in a sufficient detail. For example, the following screenshot shows a comparison of the conventional application modules in the configurations.

In most cases, comparing the metadata objects in this way, we can update the type configuration with the preservation of all improvements. Of course, it all depends on the complexity of the changes made, because if the entire configuration is "rewritten several times", the update from the official package of updates of the supplier can be impossible.

Print

For convenience, you can display a list of all configuration changes to a tabular document and use it upon subsequent update when you need to select ways to combine modules, give the priority of the basic configuration or configuration of the supplier. To save the results of configuration comparisons, you must form a detailed comparison report for the entire configuration.

By clicking on the "OK" button, we will receive a detailed report on changes in a typical configuration in a table document format that 1C platform: The company allows you to save to other formats (for example, Excel Table).

This is ready, proceed to update. We do not forget to look at the correctness of updating metadata objects in accordance with the received report.

The window controls the comparison process and combining configurations or external reports and treatments.

To compare and combine configurations, select " Configuration - Compare, combine with a configuration from a file".
To compare and combine external handlers (reports), click the "Actions" button of the report editing window / processing and select " Compare, combine with ".
To compare and combine processing (report) with external processing (report) in the context menu of the report / processing, select " Compare, combine withexternal processing, report ... ".

This column displays the main configuration objects (report / processing). Also in this column in each modified or added (that is, there is no object that is missing in the main configuration) of the object, which defines the object to participate in the merger process.
For added objects, this means copying from the downloadable configuration to the main, the operation will be determined by the specified rules. Also, this check box establishes the rules for ordering objects whose order has changed. Subsequently, this order can be changed.
Each object in the tree has a context menu, which consists of a part of the standard configuration tree menu and commands specific to the combination process. For any element of the tree (both the object of metadata and simply branches of subordinate objects), which does not apply to the branches of added or remote objects, there are commands Install the merge mode for subordinate objects and Install order for subordinate objects. For metadata objects present in both configurations (associated with each other) there is also a command Cancel object compliance. For metadata objects that do not have a mapped object in another configuration, but having the ability to match (that is, in another configuration there are unstable objects of a similar type), a command is present.

Install mode for subordinate objects.

Allows you to set the merge mode for the entire tree of objects subordinate to this. When group installation, you can select three modes, and.

Configuration Configuration Mode	Description of the regime
Take from the downloaded configuration	The object will be replaced by the appropriate object from the downloadable configuration.
Combine with the priority of the main configuration	If the object supports the association, it will be combined. If the object supports a priority combination, it will be combined with the priority of the main configuration.
Combine with priority downloadable configuration	If the object supports the association, it will be combined. If the object supports a priority association, it will be combined with the priority of the downloadable configuration.

Establish order for subordinate objects

Allows you to set the procedure of subordinate objects in all objects subordinate to this. Two options are possible.

Cancel object compliance For mapped objects, cancels compliance. After that, objects will be considered different. Set the compliance of objects For objects that do not meet in another configuration allows you to select the appropriate object. File (Second Configuration) This column displays the facilities of the downloadable configuration (report / processing). Each object has a context menu, similar to objects from the main configuration. Combine and the procedure for subordinate objects . This column displays the status of objects with a modified order, as well as the merge mode is set for objects and specific properties. Objects with a modified order relative to the associated allow to set order (watch The procedure of subordinate objects). It is important to note that the task of the object of the object means a task of the order of all objects of this type having a general owner. The merge mode can be specified for objects and specific properties. For objects, set the mode in the same way to set the mode for subordinate objects of the context menu. For a specific properties, the mode is determined by the type of this property. If the property does not support the association in principle (for example, the number) for it, only substitution mode is possible ( Take from the downloaded configuration). If the property supports a simple association (for example, lists of links to metadata objects), then mode is available for it. Combine. If the property supports a priority association (for example, multilingual lines), all the modes described in the command are available for it. Set the procedure of subordinate objects.
If multiple languages \u200b\u200bare used in the configuration and in the setting, the selective comparison mode in languages \u200b\u200bis specified, then for such objects it is compared and combined with the language specified in the language setting. Color design of objects . Decipheres the color design of object status. The following options are possible.

Status	Description
Unchanged	The object is fully identical to the appropriate object in another configuration.
Changed	The object is changed relative to the corresponding object in another configuration. Changes can be among the properties of this object or among objects subordinate to this.
Uncertain	The object has a correspondence in another configuration, but the status (unchanged or modified) is currently unknown. To determine the status, you need to re-compare using the Update button
Only in the main one	The object is present only in the main configuration.
Only in the downloadable	The object is present only in the downloadable configuration.
Changed the order of the object	The configurations changed the order of the respective objects.

Filter Determines how objects in the tree are displayed with what statuses.

Filter	Description
Show everything	Show all objects that exist in configurations
Show distinction in configurations	Unchanged objects will not be shown
Show change	Only replaced objects will be displayed.
Show present only in the main configuration	Only objects from the main configuration that do not have conformible in the downloadable will be shown.
Show present only in the downloaded configuration	Only objects from the downloadable configuration that are not conformible in the main
Show present only in configuration expansion *	Only objects will be shown from the configuration expansion that do not comply with the downloadable
Show present only in the file *	Only objects from the downloadable extension file will be displayed.
Show unchanged	Only unchanged objects will be shown.

* - Used when comparing / combining configuration extensions. Actions In this menu, you can make actions to manage the merge. Search for unsolvable references to removed objects Searches for unsolvable links to remove objects. The result is displayed in the message window. Download Settings from the file The current merge settings are replaced with the settings stored in the specified file. In this case, the path to the storage file is changed to the selected one. Add settings from file The current settings add merge settings from the file. In this case, the path to the saving file does not change. Save settings to file Saves settings to the current settings file. If the current settings file is not selected, the file selection dialog opens. Save settings to file as ... Saves the set settings to a new file. Set default settings Restores the settings that were used when opening the comparison / association dialog. Combine modules Performs combining marked unindicted modules for which one of the modes is installed " Combine ...". Install mode for all Similar to setting the merge mode from the context menu of the configuration root. Mark on the main configuration subsystems / Mark by file subsystems Allows you to set the association flag for all objects related to the specified subsystems. Configuration Comparison Report Generates a report on the comparison of two configurations (reports / treatments). Refresh Performs a comparison of configurations to clarify the status of associated objects. Parameters Opens a comparison / association configuration dialog.

If you select a specific object in the comparison window, you can cancel the compliance of objects in the context menu commands, open the object, get a comparison report. The composition of the context menu commands depends on the type of object. So, for layouts there is a show of differences in layouts, for modules - show differences in modules, etc.

If checkbox " Save settings automatically"Installed, before performing the setting operation will be automatically saved.

To merge in accordance with the specified rules, click the button Perform.

see also: