The error Cannot read properties of undefined (reading 'length') when generating the "Subconto Analysis" report in 1C:Accounting for Kazakhstan is usually related to accumulated cache and is resolved by clearing it. This is a software interface glitch, not a problem with accounting data: the figures in the database are not corrupted, and the report itself is generated correctly after clearing the cache. Below is what exactly this error means, how to fix it step by step, and what to pay attention to so that it does not recur.
Why the error occurs
The message Cannot read properties of undefined (reading 'length') is an interface script execution error. It occurs because outdated or corrupted interface data is stored in the cache, which prevents the script from correctly processing a report element. Simply put, the program accesses a form element that is actually absent from the loaded (cached) representation, and the attempt to read its property causes a crash.
Most often this manifests specifically when reopening the report or after updating the configuration/platform, when the old version of the forms remained in the cache while the logic has already changed. Therefore, there is no need to adjust postings, contracts, or counterparty cards in such a situation — the source of the problem is on the client side, not in the accounting data.
What needs to be done
The main solution is to clear the program cache. If the database is opened through a browser (web client), you additionally need to clear the cache in the browser itself and then completely restart it. Important: simply closing the tab is not enough — you need to close all browser windows and open it again.
After these actions, generate the "Subconto Analysis, Counterparties, Contracts" report again — the error should disappear.
Step-by-step troubleshooting procedure
- Close the report and, if possible, the database. End the current work session so that clearing the cache proceeds without locks.
- Clear the program cache. Delete the accumulated local cache of the 1C client. This will force the program to reload the current forms and interface settings.
- If you work through the web client — clear the browser cache. Delete the cached data and files of the site through which the database is opened.
- Completely restart the browser. Close all browser windows (not just the tab with 1C) and open it again. Only after a full restart does clearing the cache take effect.
- Log in to the database again and generate the report. Open "Subconto Analysis, Counterparties, Contracts" and build it again.
In most cases, after a full cache clearing and restart, the report is generated without an error.
Frequently asked questions
Why does such an error occur? It is related to the fact that outdated or corrupted interface data is stored in the cache, which prevents the script from correctly processing a report element.
What to do if clearing the cache did not help? Make sure that the cache is really fully cleared — both in the program itself and in the browser, and that the browser was restarted entirely, not just the page refreshed. A common cause of a "recurring" error is that the user refreshed the page (F5) instead of completely closing all browser windows, and the old cache remained in memory.
If the error persists
When a full cache clearing and restart do not help, follow the general diagnostic procedure without changing accounting data:
- Check another browser or another user. If the report is built in a clean browser or under a different user, the problem is definitely local (cache/environment of the specific workplace).
- Make sure the platform and configuration are fully updated. Interface errors often occur in an intermediate update state; correct completion of the update removes the mismatch of forms.
- Try generating the report with a narrower filter. Build the "Subconto Analysis" for a single counterparty or contract — this helps to understand whether the failure is reproduced on specific data or on the form as a whole.
- Save the error text and the sequence of actions. If a request to 1C support is needed, an accurate description of the steps and the full text of the message will speed up the analysis.
Typical mistakes
- Closing only the tab with the database and pressing F5 instead of completely closing all browser windows — the cache remains, the error recurs.
- Clearing the browser cache but forgetting about the cache of the 1C program itself (or vice versa).
- Starting to "look for a problem in the data" — correcting contracts and postings, although the failure relates to the interface, not to the accounting.
- Not fully completing the platform/configuration update and working in an intermediate state.
What to check
- The 1C program cache is cleared, the database is restarted.
- The browser cache is cleared (for the web client), all browser windows are closed and it is opened again.
- The "Subconto Analysis, Counterparties, Contracts" report is built again after clearing.
- The error is not reproduced in another browser or under a different user.
- The platform and configuration are fully updated, without a "stuck" intermediate state.
After completing these steps, the "Subconto Analysis" report should be generated correctly, and the message Cannot read properties of undefined (reading 'length') should no longer appear.