Editing of data for this period is prohibited. Changes cannot be written. Editing registers Change prohibition checks not found

Processing allows you to read data from any accumulation register, accounting register or information register, edit them and record them again. To do this, you need to select the desired register. Then set the appropriate values ​​in the selection fields. For a slave register, the registrar only needs to specify the registrar itself. Click the Read button. Data from the register will appear, which can be edited. After that, this data is entered into the database using the Write button.

It is possible to edit the accumulation register not only with selection by the registrar, but also with selection by one of its dimensions (see figure “Selection by dimensions of the accumulation register”).

Register entries can be edited based on the data in the first line for a specific field. To do this, after reading the register entries, you need to place the cursor in the desired column, and by clicking the “Fill in the first line” button, it will be carried out in the selected column through all lines to the value in the first line.

Register entries can be edited in any way. For this after reading register entries you need to type the text on the right and click the Process button (see Fig. "Random processing of register entries").

If it is necessary for a set of register records to be written with the Data Exchange.Load attribute, then you need to set the corresponding attribute. (see Fig. "Loading Symptom").

Editing data retroactively is not a problem for users with full rights. To do this, uncheck the “Apply ban date for users with full rights” checkbox. If for some reason it is undesirable or impossible to remove it, but it is possible to work with the register that needs to be edited, then with this processing it is possible to edit the available register, but this requires a slight modification of the configuration. To avoid the procedure for checking the prohibition of editing retroactively, use additional parameter: "RecordSet.AdditionalProperties.Insert("Do NotCheckDate", True);". For it to work, it is necessary to make changes to the procedure for checking the ban date. In the SCP, the following changes can be made to the event handlers for subscriptions to the BeforeWriteAccumulationRegisterDateEditingBanDate and BeforeWriteInformationRegisterDateBanEditDate:

// Checking the possibility of changing register records (date of prohibition of changing data) // Procedure Before Recording the Accumulation RegisterChecking the Availability of the Period (Source, Failure, Replacement) Export If Failure OR Source.Data Exchange.Load Then Return;

endIf; //- //Checking the Period of Register Records (Source, Failure, "Accumulation Register"); //- //+ If Source.AdditionalProperties.Property("Don'tCheckDate") AND Source.AdditionalProperties.Don'tCheckDate Then Failure = False;

Otherwise, Check RegisterRecordPeriod(Source, Failure, "Accumulation Register");

endIf; //+ #If NOT an OuterConnection Then If Refusal Then Report("Editing data for this period is prohibited. Changes cannot be written...", MessageStatus.Important);

endIf;

#EndIf End of Procedure // Before Recording the Accumulation Register, Checking the Availability of the Period // Checking the possibility of changing register entries (the date of prohibition of changing data) // Procedure Before Writing the Information Register, Checking the Availability of the Period (Source, Failure, Replacement) Export If Failure OR Source.Data Exchange.Load Then Return;

2. endIf; //- //Checking the Period of Register Records (Source, Failure, "Accumulation Register"); //- //+ If Source.AdditionalProperties.Property("Don'tCheckDate") AND Source.AdditionalProperties.Don'tCheckDate Then Failure = False;

Otherwise, Check RegisterRecordPeriod(Source, Failure, "Information Register");

endIf; //+ #If NOT an OuterConnection Then If Refusal Then Report("Editing data for this period is prohibited. Changes cannot be written...", MessageStatus.Important);

  • endIf;- the date of prohibition of changes is set simultaneously for all organizations and user roles;
  • Date of ban by organization- allows you to set different ban dates for organizations, without division by role;
  • Date of ban by organization and user- allows you to set different ban dates for organizations based on users and (or) user groups. If the user is a member of several user groups, then the minimum date set for the user groups is taken as the limiting date.

For edition 3.0:

Go to the “Administration – Support and Maintenance” menu, check the “Change prohibition date” checkbox and click the “Configure” link to set the required setting:

The following values ​​are available for the “Set ban date” value:

  • There is no prohibition on changing data- in this case, all previously set ban dates are disabled;
  • For all users- in this case, the fields “Method of specifying the date of the ban” and “Date of the ban” become available.
  • By users- this feature can be used if the ban date needs to be set for a specific user or group of users or different users need to set different meanings ban dates.

The following values ​​are available for the “Method of specifying the ban date” value:

  • endIf;– with this method, one ban date is set for all program data elements;
  • By objects– ban dates are specified by program objects. Each object has its own ban date. If this value is selected, then a list becomes available to which you can add objects (using the appropriate command) and specify a different ban date value for each object.

Often, accounting programs need to prohibit changes to old documents. For example, after the reporting has already been submitted. Human factor plays a huge role when working with any accounting program. To prevent an employee from ignorance or accident from making changes to such documents, 1C 8.3 Accounting 3.0 provides a mechanism for period closing dates.

Where can I find the ban date in 1C 8.3? In the "Administration" menu, select "Support and Maintenance" (if you have the appropriate rights).

In the “Routine Operations” subsection, check the box for “Change Prohibition Dates”. To the right you will have the opportunity to go to its settings.

After clicking on the hyperlink to the settings that appears, the corresponding form will open. First you need to indicate whether the ban date is set for all users, or only for certain ones. These two methods differ only in that in the second case it will be necessary to specify a list of users or user groups to which this ban will be applied.

Setting the ban date “By users”

If the setting type is “By User”, ban dates are configured for each user or group of users. To do this, you need to select the appropriate line and specify the value in the “Banning date” field.

Setting the ban date “By objects”

In the 1C Accounting 3.0 program, it is possible to differentiate the ban date by organization. This method relevant when the program keeps records of several organizations at once.

At the bottom of the form, in the “Other ways to specify the ban date” section, select the “By objects” drop-down list item. In the tabular part that appears, those organizations are indicated whose data editing should be prohibited. Each organization has its own date.

If this setting is not carried out for all users, then each has its own list of organizations and dates. It is permissible for one user to set the “By Objects” method, and for another to set the general date.

General ban date

In the case where the ban date is common for both users and organizations, the setting will look like the figure below.

Dynamic ban date

Rigidly setting a ban date is often inconvenient, as it requires constant monitoring of relevance and change. There is no guarantee that it will be installed on time next time.

To avoid mistakes and unpleasant situations in the future, it is recommended to set “End of last year/quarter/month/week” or “Last day”. This setup method will automatically reset the ban date.

Setting the ban date for downloading data

In the case when you have configured synchronization with other 1C databases and unwanted data may end up in past periods, use the data download prohibition date setting.

In the "Administration" menu, select "Data Synchronization".

When data synchronization is enabled, you will have access to the “Download prohibited date” checkbox. Install it and follow the hyperlink that appears to go to the settings.

Setting the download prohibition date is similar to setting the data editing prohibition date. Their difference lies in the fact that here, instead of differentiation by users, division by information databases, with which synchronization is performed.



2024 wisemotors.ru. How it works. Iron. Mining. Cryptocurrency.