Instructions
Select two databases - a working one and a copy of it. In the latter, display the changes that distinguish it from the standard program configuration, which is available when you start working with the program after installing it.
Create a .cf file because the manufacturer's website only provides users with a .cfu file. You will need it to complete next step associated directly with updating the changed configuration.
In the working database, go to the “Support” menu, then click on the “Configuration update” item, select the previously created .cf file. In the database copy comparison window that appears, uncheck the boxes that you recently updated.
Compare and consolidate data using the Support menu. In the “Support Settings” option there will be a “Compare and Merge” sub-item. Please pay special attention that in this case you should only compare and merge the data without checking the checkboxes. This operation is necessary only for the purpose of establishing order and identifying the sequence of objects in the current configuration with the order and sequence of objects located in the update file.
Next, go to the same menu items in “Support” again, perform the “Compare and Merge” operation again, exactly the same as last time. Perform work on objects, analyze the results, compare the identified working database from the copy, and in the copy of the database, specify exactly those items that were changed. Transfer changes from new configuration supplier. Save the changes by pressing the F7 key.
Repeat the above steps several times before you start working with real production databases. Remember, the more times you go through this sequence before you start working directly with the data that is important to you, the better.
note
Configuration objects that you have added cannot be changed; you may lose data.
Practice updating on copies; do not start working without certain skills.
There are standard and non-standard configurations for the 1C: Enterprise application. A standard configuration is released by the developer and used by the end user in its original form, while a non-standard configuration can be written from scratch or modified based on the standard one.
Instructions
Determine which specific configuration of the 1C: Enterprise program is installed on your computer, since the methods for updating the configuration will be different. If you are using a standard configuration, then you simply need to perform the “Load modified configuration” action. If you are the owner of the program, then follow these steps.
Prepare the following objects for the configuration update. First, you must have the configuration itself installed. Secondly, find the typical configuration of the release you are using. Thirdly, you will need to find the typical configuration of the latest release of the version you need to get as a result of the update. Fourth, make a copy of your configuration file installed version program "1C: Enterprise".
A non-standard 1C configuration is when: 1) the 1C configuration was written from scratch by the programmer independently, 2) the 1C configuration was standard, but changes were added to it, even if one property was added.
In this article we will look at how it is necessary to correctly update 1C configurations, as well as several techniques for softly changing standard configurations, i.e. correct change, which will not affect the possibility of further updating.
In order to make any changes to the standard 1C configuration, it is necessary to unlock the change to the standard 1C configuration, and in some cases “remove it from support”.
In the most optimal update option, the 1C configuration can be updated completely automatic mode, this is possible when we do not allow configuration changes. Quite often it is necessary to enable configuration changes because adaptation is necessary application solutions according to the customer’s business requirements, we will focus on this option.
Before you update it is highly recommended to do backup copy database, this can be done through the Administration/Upload infobase menu.
There are 2 update options: a) Updating 1C through support (call through the Configuration/Support/Update configuration dialog) and b) through Comparison merging with the configuration from a file. It should be noted that the difference between these two points is that in the first case, both the main configuration and the supplier configuration are updated, and when comparing merging configurations, only the main configuration is updated, the supplier configuration remains the old one. Therefore, the most recommended option is to update via Update Configuration. To update via Configuration Support, the vendor's CF or CFU delivery files are used, which can be found by searching, in the template directory by specifying the path on the Internet, or by directly specifying the path to the required file on your hard drive.
When updating the 1C configuration without the ability to make changes, the update after selecting the update file occurs automatically; if the ability to make changes is enabled in the configuration, then after selecting the update file a configuration comparison window will be displayed. In this dialogue we can see how the system offers us to update our non-standard 1C configuration. At the bottom of the dialog box there is a corresponding legend for object statuses: “Object Compliance Statuses” indicate a comparison of the “Main Configuration” and the “New Configuration”, “Object History Statuses” indicate a comparison of configuration objects with the “Old Supplier Configuration” objects.
By checking the boxes next to objects, you can choose whether the current configuration object will change or remain old, as well as how to change the object. In the action menu, you can check boxes for subsystems (this is useful if the configuration is supported by several suppliers). Also in this menu it is possible to specify the priority of merging for all objects at once; by default, the system considers the supplier’s configuration to be a higher priority. The filter settings allow us to specify which configuration objects we should display in order to be able to specify the merging mode in detail. There are several standard filter templates, and you can also specify filters for each pair of configurations being compared. It is possible to set the “Show only twice changed properties” checkbox in the “Filter” settings; this will allow you to filter out objects whose updating did not result in conflicts between the supplier’s changes and the modifications of these objects:
So, the result will be a list of objects that were changed twice during the finalization of the standard configuration and in the new supplier configuration. If you agree to the update, then previously made improvements to 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, a preliminary comparison should be performed solely to reduce the amount of work later. The assessment is not accurate and quick - “by eye”. If there are more changes in the object in the new supplier configuration, then we leave the instance of the supplier object. Leave a checkmark. Then you will need to transfer changes from the working configuration. If there are more changes in the object in the working configuration, then we leave an instance of the working configuration object. Uncheck the box. You will then need to migrate the changes from the provider configuration. You can do things a little differently with modules, because... It is possible to compare modules procedurally.
Those. if in our 1C configuration and in the supplier’s configuration various module procedures are changed, then by checking the boxes correctly we will save ourselves from manually transferring code changes. To get to this, you need to click the button in the form of a magnifying glass next to the name of the mode for combining modules:
When displaying a menu of actions on an object (for example, by pressing right button mouse) we can call up a report on object comparison.
To confirm the 1C update, you need to select the menu item Configuration/Update database configuration.
To refuse the 1C update, you need to select the menu item Configuration/Return to database configuration.
Several rules that simplify future updating of 1C configurations:
The basic rule for updating 1C: you need to add new objects, because... When updating, new objects are not affected by the system
When changing the texts of modules, it is also advisable to add your own new procedures and functions, and call your new ones from existing ones
Using event subscriptions, thanks to this you can modify standard mechanisms without changing the standard code
Using standard configuration functionality
Programmatic creation of form elements (In the FormCreationOnServer event)
Thank you!
The 1C licensing policy provides for the possibility of making and saving modifications to standard configurations, and, accordingly, the possibility of updating them.*
*Modified or non-standard 1C configurations are software on the 1C:Enterprise platform, which is part of or constitutes a fully automated enterprise management system, which has undergone a number of changes due to the needs and specifics of the business, in terms of the forms and composition of directories, documents, roles, modules, etc., therefore updating the configuration 1C with changes is not at all the same as updating a standard solution.
Updates released by 1C are aimed at fixing bugs and introducing changes and additions required by law. New configurations that have recently entered the market are characterized by the release of a large number of updates of the first type. For configurations with functionality aimed mainly at compiling regulatory reporting, for example, “1C: ZUP”, “1C: Accounting”, more updates of the second type are released.
The specificity of updating non-standard configurations is the need to make all changes to the latest 1C release, while fully maintaining previously made improvements. This is a non-trivial task, the solution of which does not have a standard script, which means it cannot be fully automated. For this reason, manual operations that require the participation of a specialist prevail in the methodology for updating non-standard configurations.
The implementation stages of updating non-standard configurations are not affected by the amount of existing improvements. Briefly they can be described as follows:
- Search and comparison of changed objects;
- Making updates from a new release;
- Introducing previously made changes that were “overwritten” at the previous stage;
- Checking compatibility and operation of processes.
The difference will be in the implementation time: if there are a lot of improvements, the process will correspondingly take longer and require concentration, attention and manual checking.
Let's consider updating a non-standard configuration for the 1C environment using the example of “1C: Trade Management” (release 2014) to the next available release.
This is a very simple example, but as mentioned above, updating a more complex configuration, of course, will require a lot of time and concentration on the part of a specialist, but will have the same stages - updating (to a new standard configuration), working with reconciliation of entered and changes made, etc.
Before updating the configuration, you should download the infobase. This action is recommended to be performed before any manipulations with all databases without exception, and especially with non-standard ones:
Unloading information base completed:
Please note that if the configuration had not been finalized, that is, it was standard, then in the Configuration window opposite the name, next to the yellow cube, a lock icon would also be displayed:
In the Configuration menu, select “Support” and “Update configuration”. In fact, at this stage, the actions completely coincide with the process of updating a standard configuration:
Depending on the size of the base and its modifications, automatic search Available updates may take some time. Therefore, it is worth, despite the recommendations, select the “Select update file” option and independently, after unpacking the archive with updates and saving them, specify the path manually:
Window with background information, instructions and sequence of updates:
Configuration comparison window. On the left in the tree the status of the existing configuration is displayed, on the right – information on the new, standard version. Sections that have undergone changes are also highlighted. Next, we need to find out which sections were changed on our part and simultaneously underwent changes in the new configuration:
In order to find out which typical metadata objects have been changed previously and will also be changed when installing a new provider configuration, you must select “Show only twice changed properties”:
Only objects that meet this condition remain:
By expanding the metadata tree, you can see which specific objects will be changed. For getting detailed information, click right key select the modified object:
You can evaluate changes at the code level using “Show differences in modules”, but since they also need to be remembered in order to be made after installing updates, we create two reports: “Report on comparison of main configuration objects with the old vendor configuration” (available improvements) and “New Provider Configuration Object Comparison Report with Old Provider Configuration Objects” (updates).*
*Let's understand the terminology:
- “Main configuration” – a non-standard configuration that needs to be updated;
- “Old vendor configuration” – typical configuration from which updates were last installed;
- “New supplier configuration” is the one we are updating to now.
We customize the report form and upload it. The list of previously made changes has been recorded:
After downloading the reports, go directly to the update and click “Run”. The configurator offers the update rule “Take from the new supplier configuration” (it is indicated in the third column). This means that all modifications will be erased and replaced with standard updated objects. It’s not worth changing this rule to the tempting “Merge Mode”, because automatic merging will lead to chaos. Still, it’s better to take the time and make the changes manually:
In the window with general information about removing the configuration from support, nothing needs to be changed. Clicking "OK" will merge the objects. Next, launch “Enterprise” and record the changes to accurately complete the update process:
We accept the list of changes:*
We launch debugging via F5 and receive confirmation of the legality of the updates:
After confirmation is received that the process of rolling out updates is completely completed, you should return to the configurator, go to the twice changed metadata objects and manually make the committed changes at the code level, using the downloaded reports. In conclusion, we add that after this, it is necessary to check the correctness of the settings and the adequacy of the work processes.
Atypical 1C configuration (modified) is automated system management of the enterprise, which has undergone a number of changes, due to the specifics or needs of the business.
When the first configuration becomes popular and is used in many companies, it becomes standard.
In the second type, the developer himself makes changes, additions and improvements over time, making the settings more convenient or relevant. At the same time, if the organization is satisfied with the configuration, then there is no need to update it to a new one.
But if a number of serious changes were made to the legislation (for example, the accounting algorithm was changed), then there are 2 options for what to do with the updates:
- update to a new standard version;
- update the non-standard 1C configuration yourself, taking into account changes in legislation.
The problem with updating non-standard configurations is that this task cannot be completely automated, since there is no standard script. Therefore, when a 1C update is carried out atypical configuration There must be a specialist present who can perform all the necessary manual operations.
For example, let's take the atypical configuration of 2014 “1C: Trade Management” and its update to the next available release.
Regardless of the configuration, all stages of updating the program will be the same, but for some it will take less time, for others it will take more. The duration depends on the number of modifications. At most, it may be necessary manual check, in case there were a lot of improvements.
Step-by-step instructions on how to update a non-standard 1C configuration yourself
Upgrade steps:
- Uploading the information database.
- Go to the “Configuration” menu. There we select the “Support” menu item and then “Update configuration”.
- After the previous step, we upload the report form, having previously configured it.
- Let's move on to the update process itself. To do this, click the “Run” button.
- An information window opens with data and settings selection elements. You don't change anything about it. Click "OK".
- Let's launch Enterprise.
- For the update to complete, you must accept the changes to context menu which opened.
- Using the F5 function, you receive confirmation that all updates made are legal.
After the last point, when a pop-up window opens confirming the update, you need to return to the configurator, go to the updated metadata objects and manually make changes to the program code yourself.
Loading...
