Business Central Support Ticket: What to Include and Why

A Business Central support ticket that says "posting doesn't work" usually starts a round of questions before anyone looks at the problem. Which environment, which company, which document, which field, which value, which error. Most of the delay in Business Central support comes from that missing context, not from hard bugs. This article lists what a reproducible report contains, shows where Business Central already exposes the technical details support needs, and ends with a copy-ready template.

Why tickets stall before anyone debugs

A support engineer cannot fix what they cannot reproduce. Reproducing an issue means standing where the user stood: same environment, company, record, and sequence of actions. When any of those is missing, the first reply is a question, and the answer often comes back from someone who no longer remembers the exact steps.

The person who reports an issue is rarely the person who fixes it. A job queue support handoff closes that gap for scheduled work; a well-written ticket closes it for interactive work.

What a reproducible report contains

Where it happened: environment and company

A Business Central online tenant can hold several environments. Microsoft describes production and sandbox environments as serving different purposes: production runs the business, while sandboxes are for development, testing, and training. A sandbox created from production data can look identical to production. Name the environment type, the environment name, and the company.

The environment matters for a second reason. When an environment is created as a copy of another, Business Central stops job queue tasks in the copy and blocks outbound HTTP calls from extensions by default. An issue involving a scheduled job or an integration may not reproduce in a copy until those are re-enabled, so say whether it touches either.

What was open: page, record, field, and value

Name the page as Business Central shows it, for example Sales Order, and the record, for example the order number. If a field is involved, give the field caption and the exact value entered, including units, the date format, and any zeros at the start of a code.

The browser address helps. The web client URL can carry the environment name, the company, the page ID, and a bookmark parameter that identifies the record shown on a card or document page. Pasting the address from the affected record gives support a direct path to it. Microsoft notes that URL filters can be sensitive, so review the address first.

What was done: exact steps

Write the steps as a numbered sequence from a known starting point: which page, which action, which fields changed, in which order. Include anything that differed from the usual routine, such as a new item or a changed setup. If only one user sees the issue, say so. Microsoft notes that many warnings and error messages come down to setup or missing permissions, and comparing two users helps isolate both.

Expected result and actual result

Two sentences are enough: "Expected: the invoice posts with the discount. Actual: posting stops with the error below." Without the expected result, support cannot tell a defect from a setup question.

The full error text and its technical details

A cropped screenshot of an error loses most of what support needs. Business Central provides the technical details as text, and that text is the most useful part of the ticket.

Where Business Central keeps the technical details

Copy details on the error dialog

Starting in version 22 (2023 release wave 1), the error dialog includes a Copy details action. According to Microsoft's guide to understanding the error dialog, the copied text contains the error message followed by:

• Internal session ID

• Application Insights session ID

• Client activity ID

• Time stamp on error, in UTC

• User telemetry ID

• AL call stack

Two of these do most of the work. The Application Insights session ID is recorded in the operationId field of telemetry, so a developer can query what happened in that session before the error, provided telemetry is enabled for the environment or app. The AL telemetry operations guide covers that setup. The AL call stack shows where the error happened at the top and what the user started at the bottom, with the object, trigger, line, app, and publisher for each step. That tells support whether the issue sits in the base application, a partner app, or a per-tenant extension.

Microsoft's article on warnings and error messages describes a Share details menu on error dialogs and a Share icon on inline validation errors. Share details to Teams and Share details via email copy the details and add a link to the page where the error occurred. Whichever label a version shows, paste the full text into the ticket, not a summary.

The Help and Support page

The question mark in the top-right corner opens the Help pane, which links to the Help & Support page. According to Microsoft's resources for help and support, its Troubleshooting section shows the latest error message, the current Business Central version, and a link to page inspection. The Report a problem section shows the partner's support contact, if configured, and lets a user switch on additional logging before repeating the problem.

Microsoft's guidance on managing technical support adds two details. The Troubleshooting section shows the Microsoft Entra tenant ID, which a partner uses to identify the tenant. The View the last known error link returns the text, code, call stack, and object for the most recent error raised by application code. It cannot open errors generated by the platform.

Page inspection, and who can use it

Page inspection shows how a page is built and where its data comes from. Open it from Help & Support with Inspect pages and data, or press Ctrl+Alt+F1. The page inspection reference lists what the pane shows: the page name, ID, and type; the source table; every field in the source table for the current record with its value, including fields not shown on the page and fields added by extensions; and the filters in effect. In 2026 release wave 2 and later, an Extensions tab lists the installed extensions that add or extend the page or its source table, with ID, name, version, and publisher.

Access is controlled by permissions. Full details require Execute permission on System object 5330, which an administrator can grant through a permission set such as D365 Troubleshoot. Users without it can still open the pane, but they see only the Page and Table fields. Those names and IDs still belong in the ticket. Opening the full table through View table also requires read permission on the table and direct execute permission on system object 1350 Run table.

A copy-ready ticket template

• Summary: one line stating what fails and where

• Environment: production or sandbox, plus the environment name

• Company:

• Version: from the Help & Support page

• User: the Business Central user, and whether other users see the same issue

• Page and record: page name, record number, and the browser address

• Field and value: field caption and the exact value entered

• Steps to reproduce: numbered, from a known starting page

• Expected result:

• Actual result:

• Error details: the full Copy details text, pasted as text

• When: date, time, and time zone of the first occurrence, and whether it happens every time

• Recent changes: new extension, update, or setup change, if known

• Impact: what is blocked, and by when a workaround is needed

Capturing the context without extra work

Filling in a template by hand under time pressure is where context gets lost. ShowMe for Business Central is a free Chrome extension from Bitta Apps built for this step. With each screenshot, it records the page URL and title, the active field's name, and the value in that field. When a Business Central error is pasted into a note, ShowMe picks out the message and the identifiers support asks for. Screenshots can be annotated, and a blur tool covers sensitive content. A finished report exports to PDF, HTML, Markdown, or ZIP, or files directly to Azure DevOps, Jira, or monday.com after a preview. ShowMe has no account and no backend server, and captures stay in the browser until they are exported or shared.

The ShowMe walkthrough covers the full reporting workflow. The extension is available from the Chrome Web Store and is listed with Bitta Apps' other free tools for Business Central. A colored environment bar, such as the one in Bitta Theme, also puts the environment name into every screenshot.

Support turnaround depends on how much of the reproduction work the first message already does. A team that agrees on one template, grants page inspection details to the people who triage issues, and pastes error details as text instead of cropping them removes the first round of clarifying questions. For organizations that want a partner working from reports like these, Business Central support and managed services describes how Bitta Apps sets up support ownership and coverage.