BC Observatoryunofficial, made by waldo
topic hubAL Developmentofficial - Microsoftreviewed - checked by Opus

Troubleshooting

Troubleshooting for Business Central development covers tools and guides for gathering information, finding causes and fixing problems. It answers questions on client tools, AL debugging and profiling, telemetry setup and analysis, and guides for migration, report and web service errors.

Open in Claudetroubleshooting.md

Path: Development > Troubleshooting · tier official · system development · narrative reviewed (checked by Opus)

Overview

This section collects the tools and guides used to diagnose Business Central issues. The overview page lists the main tools: error dialog inspection, Page Inspector, Event Recorder, database locks, Performance Profiler and AL Profiler. It also points to snapshot debugging and telemetry.

The subtopics split by where you work. Troubleshooting in the client covers in-product tools, such as inspecting pages, reading error dialogs, viewing locks, finding missing indexes, discovering events, exporting report data and profiling performance. It also covers personalization, permissions and on-premises mobile app issues. Troubleshooting in AL covers the AL debugger, snapshot debugging, the AL Profiler, performance articles and printing problems.

Troubleshooting with telemetry covers sending telemetry to Azure Application Insights, the available events, analysis with KQL and Power BI, alerting and performance diagnosis. The troubleshooting guides (TSGs) give cause-and-fix steps for cloud migration problems, report errors and slow reports, and web service failures (OData, API, SOAP). Start with the overview, then pick the subtopic that matches your situation.

Key points

  • The overview page lists these tools: error dialog inspection, Page Inspector, Event Recorder, database locks, Performance Profiler and AL Profiler. It also points to snapshot debugging and telemetry.
  • Client troubleshooting also covers table information, finding missing indexes, exporting report data, personalization, role customization and permissions.
  • On-premises mobile app issues are covered under client troubleshooting.
  • AL troubleshooting covers the AL debugger, snapshot debugging, the AL Profiler, Page Inspection, performance articles and printer errors.
  • Telemetry troubleshooting covers turning on telemetry to Azure Application Insights, the available events, and analysis with KQL and Power BI.
  • Telemetry pages also cover alerting and diagnosing performance problems.
  • TSGs cover cloud migration problems, report errors and slow performance, and OData, API and SOAP web service failures.
  • TSGs explain causes of errors, which telemetry to check and how to fix them.

Subtopics

More Learn pages

Business Central pages and reports

The pages, reports and queries this hub’s Learn pages name (ms.search.form, API reference), joined to the code by exact object id (data/index/docs-objects.json); a page shows the table it runs on.

Learn also names 2 objects with no object page: page/9830, page/9831.

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.

What Learn documents here 8 of 31 Learn pages

Show 23 more