Not long ago, 1C was pleased with the release of a new version of the application solution 1C: Enterprise Accounting 3.0 and was saddened by the subsequent cessation of support for version 2.0 in the spring of 2014. A little later, at the request of partners, the developers agreed to continue supporting version 2.0 in terms of regulated reporting until the end of 2014.

The solution is the long-awaited continuation of the legendary series accounting programs. It has a fundamentally new interface (the so-called managed application), which opens up new possibilities for users: it is possible to work in thin and web client mode, host applications in the cloud, generate reports in the background, and others. In addition to interface changes, there are some improvements in terms of accounting: the accounting module has been expanded wages, tax accounting has become more convenient and logical.

Required release

Let's start with the basics: what is needed for the transition? What is needed is a release of version 2.0 configuration, from which you can switch to the current version. To understand which release is needed, you need to find information on the current version suitable for updating on the website http://users.v8.1c.ru. For example, the current version is 3.0.27.7, which can be updated from release 2.0.53.6.

Adaptation of configuration improvements

If the configuration is atypical, the first and most difficult task that the “implementers” face is to transfer from the “two-room” functionality to the “three”.

To obtain a list of changes, you must compare the database configuration with the vendor configuration (check that the vendor configuration is up to date).

The following features are found here:

• All improvements made on “regular” forms cannot simply be transferred to managed forms. It is necessary to adapt the program code.
• Accounting 3.0 is inherently new program. If, for example, previously your modification was in the “Calculate Percentage of Surcharge” function in the “Receipts of Goods and Services” document module, now such a procedure may not exist at all. Here the question arises about the need for serious understanding and analysis of each modification.
• If the programmers' modifications used standard ones, with a high probability the “links” will be lost: the common modules have seriously changed: both the composition of their functions and their names (the legacy of the new BSP 2.x).
• The same situation applies to metadata objects. A large number of objects have become “unnecessary”, other objects are used instead, some have been renamed (for example, the directory “Registrations of the VIFNS” began to be called “Registrations in Tax Authorities”).

Get 267 video lessons on 1C for free:

The problem of industry “superstructures”

Currently, based on the 1C: Enterprise Accounting configuration, there are a huge variety of industry solutions. These solutions are often installed as an “add-on” to the configuration.

If we analyze the market, many such solutions are no longer supported. Everywhere for various reasons: in some places the developers left the company, in others the development organization no longer exists. Regardless of the reason, the fact remains - either we transfer the configuration “at our own expense”, or we lose the treasured functionality.

This issue can be perceived very sharply by the client due to the company's budget limitations for maintenance and support of software products.

Data restructuring and the process itself are very sensitive issues.

Restructuring may take a long time. Tables with a large number records, even on good equipment, can take quite a long time to restructure.

There were examples when the database was updated for several days, and at the end the system generated an error stating that “the information register entry ... has become non-unique.” This situation is quite possible, it is necessary to pay attention to this and add additional time to the risk bank.

The update process (launching update handlers when the program is first launched) also does not always work correctly and can repeatedly produce “surprises”.

There is no single recipe for how to avoid errors when updating and restructuring; new nuance. Before the actual transition Necessarily run the update and restructuring procedure “live” several times on server equipment - this will help you avoid unnecessary nerves at hour “H”.

Access rights

Judging by experience, problems with access rights occur quite often. After the update, be sure to check the user's ability to log into the information database. As a rule, these problems are solved by simply rewriting the user’s rights (Access Groups tab in the “Users” directory element).

External processing, reports, printing forms

Translation of external processing, reports, and printed forms is not provided in any way by 1C. To “convert” them, you need to take a conscious approach to the matter:

• firstly, the forms need to be switched to managed application mode;
• secondly, by new technique libraries of standard subsystems, preparation of such files is necessary.

(Details about creating external processing and reports in the ITS article http://its.1c.ru/db/bspdoc#content:22:1:IssOgl2_%D0%A1%D0%BE%D0%B7%D0%B4%D0 %B0%D0%BD%D0%B8%D0%B5%D0%BD%D0%BE%D0%B2%D0%BE%D0%B3%D0%BE%D0%BE%D1%82%D1%87 %D0%B5%D1%82%D0%B0%D0%B8%D0%BB%D0%B8%D0%BE%D0%B1%D1%80%D0%B0%D0%B1%D0%BE%D1 %82%D0%BA%D0%B8)

Restoring numbering

The developers themselves stated that after updating the program to 3.0, there is a problem with the numbering: it “goes astray” and starts counting again. In order to return the numbering, it is enough to create a document with the last code that was in the system.

For example, if the last Receipts document was numbered 256, we create a document with the same number set manually (256), and the next document will automatically have number 257.

For these purposes, you can write a simple processing: create a document of each type with the last existing number and mark it for deletion.

Exchange rules

If your configuration was exchanged with another using exchange rules, then with a very high probability the rules will stop working. This is due to the fact that some metadata objects began to be named differently, some details were deleted, and some were added.

For correct operation, you need to load your rules into the “Data Conversion” configuration, find the changed details and correct them. If you are sure that you know what the error is, you can correct it directly in the xml rules file by opening it in notepad.

Organizational aspects

The last point among the difficulties is organizational issues:

Justification of update costs to the client (management). This is a very difficult issue for the client. Quite recently there was a transition from 1.6 to 2.0, and now 3.0. Why should a client pay money for an update? There is only one consolation: I hope that no innovations or major updates are expected in the near future.

Estimation of labor costs for the transition. The transition time to a new version of the program greatly depends on the degree of modification of the configuration. It is recommended to try to refrain from making a premature assessment and try to agree to work “in fact”. This is due to the fact that the restructuring process can take a long time, and these problems cannot in any way be foreseen in advance.

Let's summarize and try to give some general recommendations for an easier and more comfortable transition:

• Plan your transition as early as possible, don’t wait until the last days.
• It is desirable that the transfer of functionality be carried out by the same programmers who finalized the configuration.
• Try to allocate as much time as possible to the restructuring. If you are switching from Monday, start work on Friday evening.
• Before the final update of all improvements, be sure to run the update on a test environment. Without a “rehearsal” you risk not having time to complete the update within the technological window.
• Make backups of everything you can, as often as possible.
• The transition to 3.0 is an excellent reason to refactor the code and “inventory” improvements. If you see that some functionality is not used or has ceased to be relevant, then feel free to say goodbye to it.
• Test the transferred functionality as much as possible, create a test database and launch users there.
• Create an environment for users where they become familiar with the program in advance - this will help avoid simple questions when starting to work with 3.0.
• Always have a “Plan B” in stock - if something doesn’t go as planned, be prepared to roll back to 2.0 in order not to paralyze the company’s work.

Relatively recently, the 1C company released new version application solution "1C: 3.0" and thereby stopped supporting edition 2.0. Previously, the developers, at the request of their partners, continued to support previous version, but it didn't last long.

This application solution is a continuation of the so-called legendary series of accounting programs. It has a different interface, the so-called managed application, which provides users with completely new opportunities: hosting applications in the cloud, creating reports in the background, and working in web client mode is also possible. In addition to interface changes, there are some improvements that relate to the accounting part: the salary accounting module has been expanded, and tax accounting has become more logical and convenient.

What are the features of the transition?

The transition from the 1C Accounting solution from edition 2.0 to 3.0 will undoubtedly be inevitable for all enterprises where it is used. It is important to say that the transition itself is not at all complicated and is simply an “update” of the configuration for the next one. But there are also some disadvantages. In practice, we have already gained experience in the transition of atypical configurations, which we will now tell you about. Below we will look at the features and problems that occur in configurations with a level of change that is “greater than average.”

Required Release

To switch to another configuration, you need little: release the configuration of edition “2.0”, from which you need to switch to the new version. You can find out which release is required on the website. There is information about the current versions suitable for updating. For example, today the current version is “3.0.27.7”, which can be updated from the release “2.0.53.6”.

How to adapt configuration modifications?

If the user is dealing with an atypical configuration, the first thing to do is to transfer improvements from the functionality of the second version to the third.

To obtain a list of changes, you need to compare (compare) the information database configuration with the vendor configuration. At the same time, you need to check that the provider configuration remains up to date.

In this case, there are certain features:

Improvements that were made on “regular” forms cannot simply be transferred to managed forms. Here there is a need to adapt the program code;

- “Accounting 3.0” is, at its core, a new software solution. If, for example, before this the modification was in a document module called “Receipts of Goods and Services” (function “Calculate Percentage of Surcharge”), now the above procedure may not exist at all. Then the question arises about the need for serious understanding, as well as analysis of each of the improvements;

When programmers used typical common modules in modifications, then most of all all the “links” will be lost. Now the general modules have undergone significant changes: both their names and the composition of their functions (the legacy of the new 2.x);

A similar fate affected metadata objects. A large number of them have become “unnecessary”, so to speak. Instead of the latter, other objects began to be used, and some of them were renamed (for example, a directory with the name “Registration VIFNS” changed its name to “Registration in Tax Authorities”);

The problem of industry “superstructures”

Currently, based on the configuration called “1C: Enterprise Accounting” there is large number industry solutions. These solutions are in most cases installed as an “add-on” configuration.

As a result of market analysis, many such solutions are no longer supported. This happened for completely different reasons. In some cases, the developers left the company, and in others, the developer company no longer exists. Therefore, the choice is this: lose the treasured functionality or transfer the configuration “at your own expense.”

Due to the firm's limited budget and program support, this issue can be very sensitive to clients.

Data restructuring

In general, the 1C update process, in particular data restructuring, are very delicate issues.

The restructuring itself takes a lot of time. Restructuring tables that have a significant number of records and, even with good hardware, can also take a lot of time.

There are cases when updating the database took several days, and at the end the system reported an error, saying that “the information register entry... has become non-unique.” Of course, such situations may exist, but you need to pay attention to this and additional time needs to be built into your risk bank.

The update process itself (at first launch software launching update handlers) also does not work correctly in all cases (without errors) and can sometimes cause problems.

Today there is no single algorithm of actions that would help avoid mistakes. After all, every time a new “pleasant novelty” may appear. The only thing to avoid unnecessary nerves at the hour “H”, at the beginning of the immediate transition, we advise you to run the update and restructuring procedure “live” several times on the server equipment.

A few words about access rights

Our experience suggests that quite often the average user may have problems with access rights. After updating, be sure to check your login capabilities and information database. Typically these problems can be resolved by rewriting the user's permissions (the tab called "Access Groups" in the directory entry called "Users").

Printed forms, external processing and reports

Translation of printed forms, external processing and reports is not provided for by 1C. To “convert” them you need to take a conscious approach to the matter.

To begin with, you need to transfer the forms to the managed application mode. Then we need to prepare such files using the new standard subsystem library method.

Numbering restoration process

Even the developers themselves noted that after updating the software product to version “3.0,” there are problems with the numbering: it “goes astray” and then starts counting again. In order to return the numbering, it is enough to generate a document with the last code that was in the system.

For example, if the last document called “Receipt” had number 256, then you need to create a document with the same number, set manually (256). The following document, accordingly, in automatic mode will enter at number 257.

For such purposes, it is possible to write a simple processing. This means forming a document of each type with the last existing number and designating it for the purpose of deletion.

What are the exchange rules?

If, for example, your configuration was exchanged with another using exchange rules, then in almost all cases the rules will not work. This situation arises because some metadata objects began to have different names, some details were deleted, others were added.

To work correctly, you need to load your rules into a configuration called “Data Conversion”. Then find the details that have changed and correct them. If you know what the error is, then the existing error can be corrected in the "" rules file. It can be opened in notepad.

A little about organizational issues

Among the difficulties, attention should be paid to organizational issues:

Justification of the cost of updating to the client. For the latter, this is a rather difficult question. Relatively recently there was just a transition from “1.6” to “2.0”, then a little time passed, and the configuration already needs to be changed to “3.0”. Why should the client again give his funds for an update? However, the user can be consoled by the fact that the 1C company is not planning any updates or major innovations in the near future.

What expenses should you expect during the transition? The time it takes to switch to a new version of a software product greatly depends on the degree of configuration modification itself. One of the recommendations is to refrain from making premature assessments, and instead agree to work “as a matter of fact.” After all, the restructuring process may continue much longer than planned. The downside is that the above problem cannot be predicted in any way.

Now we will draw certain conclusions and try to give advice on a more comfortable and simpler transition:

Don’t waste time, plan your transition as early as possible;

It would be better if the transfer of functionality was carried out by the same specialist programmers who were working on finalizing the configuration;

It is advisable to allocate as much time as possible for restructuring. For example, if you plan to switch from Monday, it would be better to start work on Friday evening;

Before you make final modifications, you need to run the updates in a text environment. Without the so-called “rehearsal”, there is a risk of not being able to complete the update in time during the technological window;

Backups should be made of everything and these operations should be carried out as often as possible;

The transition to “3.0” is a good reason to “take inventory” of improvements and code refactoring. If you see that a certain functionality is not used or has lost its relevance, then say goodbye to it without hesitation;

You can also test the transferred functionality more often. Create a test base and launch users into it;

Create an environment for users where they can get acquainted with software product. This will make it possible in the future to avoid simple questions when starting to work with “3.0”;

There should always be a Plan B in stock. If something didn’t work out with “3.0”, you will need to return to “2.0” so as not to stop the operation of the enterprise.

Before switching to the new edition, you must do backup copy. To do this, you need to run the infobase in mode Configurator and in the menu Administration select item Download infobase. In the dialog that opens, just specify the name of the file into which the data will be written.

Launch the database in mode CONFIGURATOR on behalf of Administrator databases or select user with rights database administrator. For a correct transition from BP 2.0 to BP3.0, you need to install the additional role ""

This can be done by selecting Configurator menu item " Administration - Users" and open the desired user in the list.

On the tab " Others"you need to check the box next to the item" System administrator (for transition to edition 3.0)" And " Full rights".

After clicking on " OK" the changes made will be saved.

The transition to edition 3.0 must be carried out only on behalf of a database user with these rights.

Stage 2. Updating the database in Configurator mode

To select the correct update file, you need to know the current configuration version. You can view the current version by clicking on the icon "About the program" or in the menu item Reference select item "About the program"

Open the database in mode Configurator on behalf of the user to whom you have given rights.

In the menu item " Configuration/Support » click « Update configuration " If item " Support" unavailable, click " Configuration - Open configuration " and repeat the action.

In the window that opens, select “ Selecting an update file " by pressing the button Next

Specify the path to the update file: External treatments N:\1C updates\Transition files from BP 2.0 to BP 3.0

In the next window, click « Ready » to start the update process.

After some time, the program will download information about the update file and you will see a window like this:

At the click of a button OK The configuration update process will begin. It may take some time.

During the update period you will receive two messages, first click YES- update the information security configuration, press the second ACCEPT- reorganization of tables.

Stage 3: Completing the update

After the update is complete, click the button "Start debugging." The database will open in mode Enterprise and you will see a message confirming the legality of the update. Check mark "I confirm" and press "Continue."

After the update is confirmed, the database will take some time to prepare the changes (the program may appear to be frozen).

You should wait for the update to complete.

This completes the transition to version 3.0.

Failed to update? Contact a specialist!

Sandbox

stranger July 8, 2013 at 12:33 pm

Transition to edition 3.0 of the enterprise accounting configuration

This is the name of the instructions on the “ITS PROF” disk in the new release materials section. Having tried to do the tricks that are described in this guide, you should have your own enterprise accounting (BP) 2.0 but, with managed forms and, apparently, card games and slutty women. All actions will be performed with the file version of the database.
I specifically waited for the disk with ITS, and discovered that the instructions published on it were not true, although they were in the updated section. Let's try to make this transition on one's own.

ITS disk screen

The picture above shows the procedure, and everything seems to be simple, but only on the ITS website in the BP 3.0 section, you will not find versions starting with two.

Screenshot of a real ITS website

Thus, the very first paragraph of the instructions leads the user to a dead end. It will not be possible to update to another, date-matching or latest version. The pre-existing update distribution from version 2.0 is not listed. But there is a complete distribution kit containing the necessary updates. Download this distribution and install it in the templates directory. The “trick” of this distribution is that it contains the file “1Cv8.cf”, which is what we need. With its help, we will create a clean BP 3.0 configuration and load our database with BP 2.0 into it.
We install platform 8.3, note the thin client file version, and web server extension modules (in order to play around with the “new” goodies in accounting). Open the “old” (8.2) configurator, and add the rights “System Administrator (for transition to revision 3.0)” to the user under whom we will update. We unload the database, close the configurator and open the “fresh” one (8.3). We create in it new base, from the template, with version 3.0, this template appeared when we installed the full distribution. Open the created database and download the download of our database. This operation may take long time. After the upload is completed, open the database (not from the configurator) and complete the update (this operation also takes a lot of time). I recommend compressing the database, since after these steps it almost doubled.
If your configuration did not contain changes (additions), then the update will most likely take place without errors, but in the case of 1C you cannot be completely sure of anything.
All. You can open the database with a thin client, publish it on a WEB server and launch 1C through a browser.
P.S:
1. Do not use 1C Denwer as a web server.
2. Publish on the web server the database that is physically located on it.
These tips will help you publish 1C on a web server on the first try.

Tags: system administration, 1s enterprise 8, accounting

This article is not subject to comment because its author is not yet