troubleshooting-index

Classify the symptom into one of four categories: standard errors, data inconsistency, operation failures, or performance issues. Then load the matching reference file, form two or three hypotheses, gather evidence with read-only queries, and confirm the root cause before acting.

Common causes include wrong document dates, out-of-order backfilled documents, incomplete cross-organization transfers, unit conversion errors, and missing stocktaking adjustments. Reconcile the receipt/issue detail line by line and adjust via profit/loss documents if periods are closed.

Skipped documents usually fail template conditions, miss account or dimension bindings, have unbalanced debit/credit rules, or carry zero amounts. Check the voucher generation report for per-document failure reasons and fix each item accordingly.

First locate the bottleneck layer: client rendering, network, server-side .NET, or SQL Server. Most slowdowns come from infrastructure, missing indexes, wide filter scopes, or data volume rather than product bugs, so avoid writing plugins as a first response.

Do not use it when the user wants to build new functionality such as adding fields or validation rules; that belongs to a solution decision workflow. It also does not cover debugging self-written Python plugins or BOS engineering pitfalls, which have dedicated skills.