1s 8 return the configuration to support. Infocraft: Housing and communal services formula. Recovering a deleted object

How to remove or return the 1C configuration for support? Is it needed or not? What should be followed and what rules exist? - we consider it in detail.

Working with 1C client support setup types.

Configuration support in the 1C program is implemented in two types.

• Full;
• Easily editable.

In the case of complete, the client always uses the ITS platform. And always the latest version. The advantage of this mode is the automation of the update process, the error-free installation of the desired version, and the use of *.cfu files for broadcasting, adapted for transmission via low-speed channels. The disadvantage will be the inability to implement application solutions for specific user requests.

The client must choose one of the modes himself, guided by his own view of his plans and methods of achieving them using automation (although some are annoyed by the very fact of the ban on editing).

Initial mode

It differs in how the client configuration was installed in the first place - as new or installed by a federation. After all, on the one hand, the distribution kit could be purchased under an ITS agreement and implemented as a new information security. Or it could have been installed, replacing the previous customer base. In both of these situations, the initial mode will be “full support”.

If the installation of the database involved combining the client’s platform with the supplier’s distribution, then the initial mode will be support with the ability to edit. For such a merger, perform: “Configuration/Compare, merge...”:

Select the file to attach the platform:

Select “Yes”:

After checking, a list of comparisons will be issued, in which you need to uncheck all the boxes, otherwise all our improvements will be overwritten:

After working with disabling checkboxes, click the “Run” button at the bottom. In the next window after “Execution”, select the option of the desired mode.

Determining and switching the current mode

It is very easy to determine the current status of the mode. This is done in the “Configuration” / “Support” / “Support Settings” dialog. The top line displays the current status. Nearby there is a button that enables access to changes:

The key is that the function of returning to the “full” status is not possible.

And to edit a new database, you can simply enable “editability” of changes. Cancellation of status is not required for this purpose.

Status management

The settings dialog (previous figure) allows (except for changing the mode) to completely abandon “supportability”. The function of creating a copy of the database from the developer (the latest version), setting languages, setting rules for individual elements, calling comparison/merging is also available there.

IMPORTANT. After executing “Remove support”, the supplier database will be automatically removed from the information base. This action is used only when the standard platform will serve as the basis for your own developments. And no further updates are planned.

Languages

An additional convenience is the ability to compare databases for individually selected languages. With such a comparison (of the client and developer databases), one of them may contain, say, in addition to Russian, some other languages ​​(for example, Ukrainian). When reconciliation is set to Russian only, rows containing Ukrainian values ​​will not be marked different (if the corresponding Russian values ​​are the same). Language setting is possible in dialogue. But it can also be configured by default. Then these values ​​will work both when comparing and when updating.

Setting up rules

Object support rules can be configured from the settings dialog. They can also be configured from the dialog for comparison/merging with the supplied platform. Let's look at setting up the rules in the first case. The default settings switches for the dialog form are set to “Object…not editable”. By right-clicking on the column on the right, a menu for setting rules will appear:

Clicking OK opens access to object-by-object configuration changes. The “Supplier object cannot be edited” rule has a certain peculiarity. It installs for identical platforms (not modified by the user). Therefore, it will not be available in the compare/merge dialog.

Recovering a deleted object

Before returning the configuration, please note:

• If you need to restore an object from a supplier, you need to use the compare/merge dialog with its platform.
• It is important to note a nuance. If such an object is deleted, then when it is copied from the platform from the supplier, an object that is logically identical to the object from the supplier will be added to the client database. But its ID will be different.
• If the object is deleted, but it is still present in the database, then you need to return to the database, but do not use the combination with the configuration from the supplier.

We looked at topics that are interesting to many - how to support a 1C configuration, how to remove it, what rules work and how they can be used.

Very often there are configurations that have been removed from support, but no global changes have been made to them. Some of the required changes could be implemented through external processing. Therefore, there is a need to put the configuration on support.

With the advent of the configuration extensions mechanism, we have a more flexible way to make the necessary changes.

Fast passage

Two options for a deprecated configuration

• The configuration can be changed - you just need to change it through the menu “Configuration\Load configuration from file”
• The configuration is completely removed from support, it is first put on support through an update, and then replaced with a standard one

The first thing any update of this kind begins with is creating a complete copy of the database. Without this, don't even start. The cost of an error may be the loss of information.

In both cases, the first task is to synchronize the configurations with the vendor configuration. This can be done with or without an update. If the release is old and it is found, then it is easier to put it on support and update subsequent configurations already put on support.

Why is that? Because a side effect of removing support is that the update slows down by a factor of 2, so in this case the update is performed on two configurations (vendor and current configuration).

1. Replacing the configuration from a file

Once you have synchronized the configurations - and the data structure and configurations are absolutely identical, you can begin replacing the configuration.

In the menu “Configuration\Support\Support Settings”:

Unlock all objects (the ability to edit) if there is a “lock”, otherwise at the next stage the message “To execute the command you need to unlock all objects” will appear:

Proceed to replacement - done through the “Configuration” menu:

2. The case is a completely desupported configuration

If you have it removed via “Remove from support”, then the configuration does not have any icons, otherwise the presence of a “yellow cube” or “Lock with a yellow cube” means that you can immediately act on the first case.

If you have it removed, you will need a configuration file, it can be any next release

Go to the “Configuration\Merge Configurations” menu and select this file:

If everything is correct (the version is suitable), then a window will appear with the message: “The possibility of combining with setting up for support has been detected,” to the question “Set up for support?” answer “Yes”

This way you kill two birds with one stone and update the configuration and put it on support.

Before clicking Execute, you also need to check the “Settings” button to allow deletion of main configuration objects (so that unnecessary and old objects are deleted).

At the end there will be a message “Configuration merging complete”

Now you perform its replacement in case 1, here you are sure that they are identical.

Hello.

Today I'll tell you what it is support for standard configurations, how important this is and why it is advisable not to remove the configuration from full support. I’ll make a reservation right away and say that this does not apply to those who develop the configuration from scratch.

Configuration Updates this is one of the functions, but the update should be easy and painless the configuration does not need to be removed from support.

Configuration is under support

For those who didn’t know, I’ll tell you :) . Standard solutions are available at supplier support. This means that 1C periodically releases new releases that correct existing errors, add new functionality, and change configurations in accordance with legal requirements.
If the user's configuration is supported, then when a new release is released, you can independently execute or execute .

The programmer should try to solve problems using standard tools, making minimal changes to standard solutions to speed up the update procedure.

The default configuration needs to be changed

It often happens that standard tools are not enough and changes need to be made to the configuration, then you need to follow the following scenario.
1. Enable the ability to make changes to the configuration.
To do this, run the command Configuration – Support – Support Setup. The “Support Setup” form opens. In this form, click the button Enable edit option. Answer “Yes” to the system’s question about the impossibility of performing automatic updates.

2. In the “Set up support rules” form that opens, set the switches to values The supplier object is not editable.

After these steps, you can provide targeted access to those configuration objects to which changes need to be made. The figure shows an example of opening access to edit the List Form of the Customer Order Document.

Adding new objects

To enable the ability to add new objects to a standard configuration, you must perform the following steps. Set up a support rule for the root configuration node The supplier object is edited while maintaining support. Flag Set for subordinate objects do not install.

That's all, if anyone wants to add I'm always for it and I'm waiting for you in the comments.
If you need to resume support or update your configuration, please visit the page.

P.S. In a programmer's practice, making changes to a standard configuration is commonplace, and there is no need to increase the complexity of system maintenance. It is necessary to be honest to your clients and the value of a programmer is not that without him nothing can be done, everything is surrounded by passwords, the code is not commented. Some also manage to insert cunning procedures, because of which the program begins to glitch and after 2-3 months you have to call the programmer again.

P.P.S When I was writing the article, I remembered a moment from the movie Lethal Force.
This is our cow and we are milking it!

Greetings, colleagues!

Everyone who is involved in supporting, maintaining and updating information databases on the 1C 8 platform sooner or later has to update their database to standard releases to make changes related primarily to changing legislation (Government minds do not eat their bread in vain).

How to do this is well described in the articles: - thanks to the authors.

In this article I would like to pay attention to the following points: when updating the SCP release from release 1.3.17 to 1.3.48, I was faced with the need to support the vendor configuration.

I’ll note right away that the main configuration of 1.3.17 in my case differs significantly from the typical 1.3.17. Most of the critical changes that were released in releases from 1.3.18 to 1.3.47 were made through comparing and combining the necessary modules and subsystems, since this method takes less time (a significant part of the SCP was radically rewritten to suit the specifics of our enterprise).

So, updating the configurations through comparison and merging, I got the main configuration 1.3.48, while the supplier configuration is 1.3.17 Fig. 1. and Fig.2.

Rice. 1. Basic configuration. Release 1.3.48.1

Fig.2. Provider Configuration 1.3.17.1

How can you set the configuration to support the current release and not lose any changes made?

Configuration - Support - Support settings - "Remove from support". We remove the configuration from the support of Fig. 3. and close the settings window.

Fig.3. Configuration is not supported

Using “Compare, merge with configuration from file” we perform a combination with the standard, current CF configuration (in this case 1.3.48.1). To the question, Fig. 4. about the possibility of applying for support o We answer “Yes.”

Fig. 4. Possibility of combining with support was discovered

Let's do it “Empty” comparison and combination of configurations, having previously unchecked all the “checkboxes” as in Fig. 5.

Fig.5. "Empty" comparison and merging of configurations

The configurator will offer to configure support rules. If the ability to edit configuration objects is required in the future, then we configure the support rules as shown in Fig. 6.

Fig.6. Setting up support rules

It would seem not very logical - but in the end the configuration object "Production Enterprise Management" - i.e. the entire configuration will be removed from support. To apply for support, do the following: Configuration - Support - Setting up support. We change the support rules for the "Production Enterprise Management" object. If you need the ability to edit configuration objects in the future, then set the parameters as shown in Fig. 7. Be sure to check the “Install for subordinate objects” checkbox. Close the settings window.

Fig.7. Support of the object "Production Enterprise Management"

After this, our configuration is fully supported by the supplier. Save and update the database configuration (F7).

It happens that certain heavily modified configuration objects that do not need to be further compared with the vendor configuration need to be removed from support. An example of how to do this is in Fig. 8.

That's all it seems. Questions are welcome. I hope that this article will be useful for someone. With respect to the community, Andrey.

The need to remove a configuration from support may arise for various reasons. Most often this is needed to make configuration changes. Also, when updating the configuration with a *.cf file, you will need to do this operation. Removing a configuration from support means that we are removing the configuration from support from the supplier (configuration developer) and the configuration is now not standard.

I would like to note that when contacting developers for help, technical support specialists always clarify whether the configuration has been removed from support. If this is the case, then you will most likely be denied help. If you make changes to the configuration in the future, problems with updating may arise, so you should not resort to this unnecessarily.

However, sometimes you cannot do without removing support. We go to the information base in the "Configurator" mode. If the configuration is not open, then click on the “Open configuration for editing” button.

The lock icon indicates that the configuration not edited. Supplier object not editable

Go to the menu item Configuration -> Support -> Support Settings.

In the window that opens, click on the "Enable editing" button

The program warns about further problems with automatic updating, click "OK"

Next, you need to configure support rules. The rule “Supplier object is edited while maintaining support” means that objects can be changed, but when updating, all changes will be lost if the checkboxes in the configuration comparison are not unchecked. The "Supplier object has been retired" rule means that all objects are open to change.

Click "OK". After accepting the changes in the "Support Settings" window, the "Enable editability" button will disappear and the message "The configuration is under support with the ability to edit" will appear.