---
title: "“Data Area Update Progress” Report in 1C:Accounting for Kazakhstan — How to Check That All Subscribers Have Been Updated"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-10-14
canonical: https://buhgpt.kz/suraqtar/otchet-progress-obnovleniya-oblastey-dannyh-v-1s-buhgalte-en
source: BuhGPT
---

# “Data Area Update Progress” Report in 1C:Accounting for Kazakhstan — How to Check That All Subscribers Have Been Updated

> **TL;DR:** Verified on release 3.0.74.2 of “Accounting for Kazakhstan” (version 3.0). You manage several organizations in a single cloud database operating under the service model. After a new release is launched, a client may report that the database is temporarily unavailable due to an

---

Verified on release 3.0.74.2 of “Accounting for Kazakhstan” (version 3.0).
You manage several organizations in a single cloud database operating under the service model. After a new release is launched, a client may report that the database is temporarily unavailable due to an update. In this situation, it is important to quickly see how many subscribers have already been updated, how many are still waiting in the queue, and which data area encountered an error. The “Data Area Update Progress” report is used for this purpose. This is an administrator’s utility that shows the update status of each data area.
Important: the report is intended for a database operating under the service model with data separation by area. In a standard local “Accounting for Kazakhstan” database for a single organization, this report is usually not available in the interface: the entire infobase is updated at once.
1. Purpose
The report shows the progress of the background infobase update for each data area, meaning each subscriber in the cloud. It allows you to see the source and target versions, the current status of the area—waiting, updating, completed, or stopped with an error—and when processing was completed. This control is required by the service administrator and an outsourced accountant managing several organizations in a shared database.
2. Where to Find It
The path depends on the interface settings and the available commands, but you can use the following sections as a guide:
- “Administration” or the database maintenance section → service model operations block → “Version Updates” or “Data Area Update Progress”.
- After opening the form, click “Generate” to obtain the current status of the areas.
If the command is missing or the object is unavailable, check whether the infobase operates under the service model with data separation and whether the user has sufficient administrative rights.
3. How to Generate and Configure the Report
The form specifies selection parameters rather than business transaction details. They help restrict the results to the required period, area, or update status.
Field or ButtonPurposePoints to ConsiderGenerateBuilds a report using the available update progress information.After changing the filters, generate the report again; otherwise, the previous result may remain on the screen.Period or dateRestricts the selection by the update start or processing time.If the period is too narrow, areas whose processing began earlier will not be included in the results.Filter by data areaAllows you to display a specific subscriber using its area identifier.If a different area is specified, the required row will not appear in the results.Filter by statusRetains rows with the selected status, such as an error or processing in progress.Before performing a general check, remove unnecessary filters to see all areas.“From” version and “to” versionShow the source and target releases, for example, an upgrade from 3.0.73.x to 3.0.74.2.These are informational report columns, not values that must be entered manually.Refresh or F5Refreshes the displayed status during background processing.Use the command again if some time has passed since the report was generated.The table displays technical information about area updates: identifiers, versions, statuses, processing times, and available error messages.
4. Operation Types (Statuses)
For this report, the important items are not types of business transactions but area processing statuses. Their names may depend on the version and interface, but their meaning corresponds to the following statuses:
- Waiting — processing is scheduled but has not yet started; the area is in the queue.
- In progress — update procedures are being performed for the area.
- Completed — processing of the area has finished, and the report shows the target version.
- Error — processing was interrupted; you need to review the available message in the area’s row.
- Deferred or not required — processing has been postponed or the area does not require the current update.
When analyzing the results, first identify the rows with errors, then check the areas that have remained in the queue or in progress for a long time. After that, compare the target versions of the completed areas.
5. What Is Generated
After clicking “Generate”, the user receives a table containing information about the progress of area updates. It may display the source and target versions, current status, processing time, and text of the registered error.
The report uses system information from the infobase update mechanism under the service model and presents it in a convenient monitoring format. Its main purpose is therefore to monitor the queue and identify areas requiring the administrator’s attention.
Generating the report again provides a more up-to-date view. This is especially useful during a bulk update, when individual areas finish processing at different times.
6. Print Forms
There is no separate approved form for this report. The result is presented as a table which, depending on the interface capabilities, can be:
- printed using the print command;
- saved in an available format, such as xlsx, mxl, or pdf;
- sent to a support specialist together with a description of the problem and the time it occurred.
Before saving, make sure that unnecessary filters have been removed and that the problematic area’s identifier, version, status, and full error text are visible. Such a file helps compare the report status with the event log entries.
7. Common Errors
“Report (object not found): Report.DataAreaUpdateProgress”. This situation is typical for a database that does not use data separation by area or for an interface in which the relevant command is unavailable. First determine the infobase operating mode.
“Insufficient rights to perform an operation on the report”. Access to system information may be restricted to administrative roles. To view the report, the user needs the rights provided by the settings of the specific database and service.
The area has the “Error” status. Open the row and read the full message. Then compare the error time with the event log, resolve the specified cause, and restart area processing using the standard administration tools. After restarting, refresh the report and monitor the status change.
The area remains “In progress” for a long time. Check background and scheduled jobs, the availability of worker processes, active sessions, and locks. Use the event log to determine whether processing is continuing or has stopped at a specific stage.
The report shows the previous status. Click “Generate” again or refresh the form by pressing F5. If a period or another filter is set, check whether it includes the current update wave.
The required organization is missing from the list. Remove the area and status filters, extend the period, and generate the report again. Then find the subscriber using the area identifier employed in service administration.
8. Questions and Answers
Is this a document or a report? It is a system report for monitoring the technical update of data areas. Its result is a table containing versions, statuses, and messages from the update mechanism.
Why can’t I see this report in my database? It is used in an infobase with data separation by area. A local database for a single organization does not require separate monitoring of subscriber updates. The command may also be unavailable due to the user’s rights or interface settings.
What is a “data area”? It is a separate portion of a subscriber’s data within a shared infobase operating under the service model. Separation allows several subscribers to be served in one database while processing progress is monitored separately for each area.
The user sees a message saying that the database is being updated. What should I check? Find the user’s area in the report. The “Waiting” and “In progress” statuses indicate that processing has not yet finished. If the status is “Error,” open the message and compare it with the event log.
How do I restart an update for an area with an error? First resolve the cause specified in the message and event log. Then use the standard service model administration command to restart it and refresh the report. Monitor the area’s transition to the completed status.
Can I determine which release the area is being updated to? Yes. Compare the source and target version columns. Release 3.0.74.x is used for the current “Accounting for Kazakhstan” line; in this example, the target release is 3.0.74.2.
Why does the user see the previous tax values after the update has been completed? The report status shows the result of the area’s technical processing. If previous values remain in documents or settings, check the document date, the tax settings, and the release being used. In 2026, the VAT rate is 16 %, the basic IIT deduction is 30 MCI, and the MCI is 4 325 ₸.
How do I send the update status to a support specialist? Generate the report without unnecessary filters, save the table in an available format, and attach a description of the problem. Specify the area identifier, the time the error occurred, and the source and target versions.
How often should I refresh the report during bulk processing? Refresh it as needed, taking into account the processing duration and the number of areas. Monitor rows with the “Error,” “Waiting,” and “In progress” statuses separately.
What should I check before considering the update complete? Make sure that all required areas are present in the report, have the completed status, and show the same target version. Check that no filters are hiding individual rows.
9. Related Objects
- Infobase update mechanism under the service model — places areas in a queue and performs the required procedures; the report shows the available information about this process.
- Configuration update and release installation — the event after which the report is used to monitor area processing.
- Event log — helps examine the sequence of events and error details if the message in the report row is insufficient for diagnostics.
- Scheduled and background jobs — participate in running system procedures. Their status is checked when the queue does not progress for a long time.
- List of data areas and subscriber administration — used to match an area identifier to a subscriber and monitor the area’s availability.
Summary
“Data Area Update Progress” is the administrator’s monitoring screen in the cloud version of “Accounting for Kazakhstan.” Its purpose is to quickly show which subscribers have already moved to the target release, which are still being processed, and where an error has been registered. Generate the report, check the filters, review the problematic rows, and compare them with the event log.
This guide was prepared for “Accounting for Kazakhstan” release 3.0.74.2, version 3.0. The installed release number can be viewed under “Help” → “About”.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_