Versioning in 1C:Enterprise ➾ History of changes to objects ➾ How to set up versioning of objects in 1C:Enterprise? ➾ What is versioning? Setting up options, roles, version recording mechanism, etc.

Imagine the situation: you are a sales manager. You have created a customer order for which you must ship the goods. We generated a sales document and discovered that the data in it did not match the buyer’s order. To find out by whom, when and what changes were made to the document, there is a versioning mechanism in the 1C:Enterprise 8 configurations.

Versioning is storing the history of changes to objects. Unlike a log, in addition to storing a history of who changed what object, when, and what, the versioning mechanism allows the system administrator to see the specific changes that users made.

The system allows you to view any version of an object or compare any versions of an object with each other. To work with the history of object changes, you must first configure their versioning. The system administrator configures and views version history.

How to configure object versioning?

On this moment The versioning mechanism is available in many standard, most common configurations, such as:

Versioning is configured by the System Administrator with full rights.

Open the "Versioning" tab and check the "Use object versioning" checkbox:

Click on "Setting up object versioning..."

When setting up versioning for each type of document and directory, you can specify:

• Do not version - the value is set to all objects by default;
• Version - the value is used to configure directories and documents;
• Version when posting - the value is used only for documents.

If the Version option is selected, then each time an object changes, the next version of the object will be written to its version history.

If a document has the Version on posting mode set, then the first version of the document will be recorded in history only after the first posting of the document. Subsequently, document versions will be recorded each time a posted document is recorded. The mode allows you not to create versions of new documents that have not been completed by the user, so as not to increase the size of the information security. We recommend that you apply this setting to all documents.

Versioning large quantity objects can lead to growth of the information base due to the storage of their versions. Therefore, it is recommended to use this feature selectively.

To view the history of object changes, open Tools/Object Change History. The command is available only to the system administrator and only for those objects that have versioning configured. In the form that opens, select an object (in the example, this is a Customer Order), select the versions of this object that you want to compare, and click the “Compare versions” button.

This command will generate a Report on object version changes (click on the image to enlarge):

During the operation of an enterprise, there is often a need to find out who, when and what exactly changed a document or program reference book.

Very often I get asked questions:

• How to see who changed the document in 1C 8.2?
• How to see who changed a document in 1C?
• How to find out in 1C who changed documents and when?
• How to find out in 1C who changed the posting in a document?
• How to see who changed a document in 1C?

Logbook

Contains information about what events occurred in the infobase at a certain point in time or what actions were performed by a particular user. For each log entry that reflects a data change, the transaction completion status is displayed (the transaction was completed successfully or the transaction was cancelled).

The logbook is available in both 1C:Enterprise mode and Configurator mode.

Access to the logbook is possible both from the Configurator mode (via the menu Administration - Logbook), and from Enterprise mode (menu Service - Logbook). In Taxi mode ( Main menu - All functions - Standard - Log book)

Type of log book(Regular forms and Taxi):

Selection in the log book(Regular forms and Taxi):

Using tools for working with lists, it is possible to upload the registration log into a tabular or, if necessary, text document (via Actions - Output list), which can later be saved, for example, in Excel, TXT or HTML format. In this case, it is possible to configure the level of events that will be recorded in the log, as well as the frequency of dividing the log into separate files (in the menu configurator mode Administration - Setting up a log).

And there it is also possible to reduce the number of entries in this log until a certain date, which is done to speed up work with the mechanism for analyzing and recording events in the system or to make irrelevant information unnecessary.

Where is the log book kept?

In the File Database: folder in the database directory 1Cv8Log - this is the directory containing the log.

If you are planning to migrate the file database and want to save the log history & you should definitely copy the 1Cv8Log folder to the category new base 1C. If you need to clear the 1C registration log in file database just delete the 1Cv8Log folder.

INClient-server database: C:\Program Files\1cv8\srvinfo\<Имя кластера сервера>\<Идентификатор базы на сервере>\1Cv8Log

From version 8.3.5.1068. The log has been significantly reworked in order to increase the speed of executing requests to the log and increase the reliability of data storage.

This, among other things, required changing the log storage format. It is now stored in a single SQLite database file. This file has the extension lgd.

Versioning objects

In some configurations 1C is implemented special mechanism"Versioning of objects".

By default, versioning is disabled; to enable it, open Service - Accounting settings - Setting up accounting parameters

Click the “Setting up object versioning” button to select which directories and documents need to be versioned (monitor who changed what and when).

By default, information base objects are not monitored, which is why the “Do not version” flag is set next to each document type. If you need monitoring to be carried out, you need to set “Version” opposite the document log of interest.

That’s it, when you close the window and click on the “Ok” button, objects will be monitored.

In order to view all the changes that someone has made in a document or reference book, you need to go to the menu: Service - History of object changes

In an enterprise, in most cases, not one specific user, but all accountants can work with the 1C program. Of course, they can perform the actions that are provided for by them. job responsibilities without interfering with the actions of other colleagues. Unfortunately, in accounting practice Situations may occur when an error suddenly appears, claims for which are presented to the direct executor who prepared the document.

Thanks to the 1C functionality, you can determine the user who generated the report or form.

If the performer assures that he did everything correctly, entered all the data without errors, and therefore cannot explain why the failure occurred, you can observe the fact of third-party interference in the process of editing the document. To perform such desired actions, it is important to figure out how to view the history of changes to a specific document in 1C.

View history

In fact, it is simply impossible to perform incognito actions in the 1C program. This is, of course, very important, since in the absence of such a function it would be possible to make changes to the program as anyone pleases, “increasing” one’s own salary, and shifting accusations of incorrect calculations onto the performer. Fortunately, the developers prevented the possibility of such fraud by equipping the program with a control function. Having figured out how to see in 1C who changed the document, you can easily find the culprit of the error. This will allow censure to be given to those who deserve it.

Verification algorithm

All actions that were performed in the 1C program are recorded in the “Registration Log”. In addition, it even records the status of the transaction, guiding the reviewer to whether the transaction was completed or canceled at the last moment.

You can open the “Registration Log” from the “Configurator” or “Enterprise” mode. In any case, the test result will be identical. Once you open the Logbook, you will be able to observe all the events that were performed in this program in chronological order.

However, many accountants can work with the 1C program, of course, filling out and generating many documents. For this reason, it is quite difficult to simply scroll through, move the slider, search for the required document and track the changes to which it has been subjected.

Fortunately, the developers have made it easier to quickly search. It's easy to find the sorting icon on the toolbar. After clicking on this button, the “Selection” window opens, in which you should immediately set a dot in the checkbox next to the “Select immediately” line.

Now you need to go to the second tab of the “Data” window. At the bottom of this tab there is a block with the same exact name “Data”. Pay attention to this block, there you will see an empty line, on the right side of which there is a button with the image of the letter “T”, click on it. Now a new window will appear in which you need to select the data type that we are trying to check now.

The next step is to select the document you are trying to find, click on the button with the image three points and select the document you are looking for from the list provided. After clicking the “Ok” button, you will have to be patient, as the program will begin the process of sorting, selecting, and everything related to the document you have selected. This process can take several minutes. The main thing is not to do anything at this moment, not to interfere, but to wait patiently.

Upon completion of this process, a list of actions to which the document has been subjected will appear on the screen in chronological order. This list identifies users as well as their specific activities. You can also determine on what day and at what time the changes were made.

ADVICE. The log book may at some point become excessively full, since actions are recorded continuously. To free the log from unnecessary outdated information, it is useful to clear it from time to time.

When you open the Logbook, you will find the option to delete entries permanently, as well as save outdated entries in a separate file. Such manipulations allow you to clear the log, but not completely say goodbye to some data, but have the opportunity to work with them in the future.

So, you can easily track who worked with the document, when, what changes they made, and whether they completed transactions, if you thoroughly study all these recommendations. practical implementation which are not accompanied by problems.

If you are developing a new configuration, you must enable the log. It will allow you to track all changes made by users in 1C. For example, you can find out who added, deleted or changed what.

But in order for this data to be recorded, you need to set up a log. In general, it is enabled by default when creating a new configuration. But if you are not using your own configurations, it is better to check these settings.

Setting up a log and viewing the change history

And so, first of all, let's set up a registration log in 1C. The settings are similar for both versions 8.2 and 8.3. Launch the Configurator, look for the Administration item and select Log Settings.

Here you need to select the last item Register errors, warnings, information, notes.

Now, for example, let’s go to 1C and create some new document or reference book, you can simply make changes. I'll create a new document.

Now, in order to view changes in the registration log, you need to go to the configurator, open the Administration menu item and select Logbook.

The Logbook will open in which all user actions are recorded. For example, I created a new document. Let's see how my actions were recorded in the log book. We see a table that has the fields Date and Time, User, Event, Transaction Status and Metadata. From them we see that I entered the program on 11/13/17 under account Administrator. In the event column you can see that I added Data. The metadata column shows which document it is.

The logbook is very convenient to store detailed information about user actions. When I launched the configuration, under whom I logged in, what I added, and what time I left the program. But in order to track the actions of each user, it is necessary that he log in under his account.

How often does your company need look who changed the 1C document?

Or how to find out which of the employees changed this or that attribute document 1s 8?

How to watch history of document changes 1C?

Module “History of Changes” based on 1C 8

Convenient and efficient tool analysis and control actions of 1C users.

Problems solved by the module "History of Changes" 1C 8:

• Eliminating the possibility fraud users with backdated documents;
• Determining who is guilty of introducing erroneous data in documents;
• Possibility of detection incorrect program operation regarding automatic changes or re-posting of documents;
• Revealing intentional distortion (change) of data, for example, entering incorrect customer contact information by unscrupulous managers;
• Opportunity see what happened with a document or reference book before changing it and, if necessary, return everything back.

Pros of the mechanism "History of Changes" 1C 8:

• All data is stored inside the 1C database, which ensures high speed search necessary information and generating the necessary reports.
• Module 1C 8 "History of Changes" has minimal impact on performance. You will hardly feel the difference when working with and without our subsystem.
• Module universal And easy to integrate into any, even standard, system-based configuration « 1C:Enterprise" versions 8.2 and versions 8.3 , including version.

Module capabilities:

The module allows you to flexibly configure the objects that will be monitored.

Viewing the history of data changes is possible directly from the form of a document or directory and is available to users who have the appropriate rights.

The control mechanism includes changes to the details of directories and documents. At the same time, both the old and new values ​​of the attribute are preserved.

A mechanism for controlling changes in 1C document lines is available. For example, changes in prices, quantities and other data in a specific line are displayed.

It is possible to see deleted and added rows in the tabular parts of documents. In this case, the program will ignore changes in the sorting of lines within the document, which is not actually a change in data. For clarity, in the report on changed data, the added rows are colored blue, and deleted ones are pink.

Logbook 1C 8.

How to find out who changed a 1C document?

It would seem that everything is simple - you can see who changed the 1C document in "Registration Log". After all, it records events related to changes in database objects, as well as events that occur when working with the database (user login and logout, errors, generation of reports). So the magazine gets very a lot of extra entries, due to which the volume of the journal is growing rapidly and problems arise both with storing the magazine and with searching for really useful and necessary information in it.

But the biggest disadvantage of the standard magazineregistration— the inability to find out what exactly was changed in the object: a property or a line in the tabular section — you won’t find the answer. And you certainly won’t know in any way what data was there before the change and what it was after.

It is also impossible to configure the built-in log so that from an open document or reference book you can see the entire history of 1C 8 changes with the click of one button. Such manipulations require a rather complex, for an untrained user, setup of selections in the log book.

Module "History of Changes" is a convenient and operational tool for analyzing and monitoring the actions of 1C users.

To Module “History of changes” 1C 8 started to do its job, it needs to be configured once. Setting up does not require much time and involves selecting documents, directories, as well as their details, which will be used to control and store the history of changes.

The cost of the module depends on the need for services for its installation and configuration. WITH Contact us in any convenient way and find out the cost.