Business Central 29.0 Preview: What Customers Should Test Before October
Business Central 29.0 is in public preview now, with general availability planned for the first week of October 2026. Existing customers should use this window to prove that their critical workflows, extensions, integrations, permissions, automations, and reports still behave the way the business expects before the update reaches production.
Microsoft says the 29.0 public preview runs from the first week of September until general availability in the first week of October. Preview sandboxes can be created or existing sandboxes can be updated to the preview version during that period, and Microsoft automatically deletes those preview environments 30 days after 29.0 becomes generally available. Review Microsoft's current 29.0 preview guidance.
Treat the preview like a business test, not a feature tour
The easiest mistake is to open the preview environment, click through a few new pages, and call the testing complete. That proves the environment opens. It does not prove that the company can still receive inventory, post invoices, run planning, close the month, process production, refresh reports, or complete the other work people depend on every day.
A better approach is to start with the business processes that would hurt most if they failed. triniT Partners helps companies improve and support Microsoft Dynamics 365 Business Central across finance, operations, integrations, reporting, and AI, and the same cross-functional view should drive major-update testing.
1. Test the transactions that carry the most business risk
Build a short list of critical end-to-end scenarios and run them with realistic data. Do not test only the happy path. Include the exceptions that force users to think, because those are often where extensions, permissions, posting setup, and integrations interact in unexpected ways.
Order entry through shipment, invoicing, payment, and return
Purchase order through receipt, invoice matching, payment, and vendor credit
Inventory transfers, adjustments, counting, costing, and availability checks
Production or assembly scenarios with shortages, substitutions, consumption, and output
Month-end posting, reconciliation, dimensions, allocations, and financial reporting
Project, service, approval, or industry-specific workflows that are critical to daily operations
For each scenario, define what a passing result looks like before testing starts. A user saying that something looks fine is weaker evidence than a documented expected result, a completed transaction, and a reconciled financial or operational outcome.
2. Test extensions and integrations as complete workflows
An extension can install successfully and still create a business problem. An integration can connect successfully and still map the wrong value, skip an exception, or fail when transaction volume increases.
Review anything that moves data between Business Central and another system, including ecommerce, EDI, warehouse tools, CRM, payroll, banking, document capture, custom APIs, and reporting pipelines. If your environment relies on several Microsoft services, the broader Microsoft cloud and business systems architecture matters too.
Run the full transaction across both sides of the connection. Confirm data direction, timing, error handling, duplicate prevention, field mapping, and what happens when the receiving system is unavailable.
3. Test permissions, job queues, approvals, and scheduled work
A major update test should include work that happens without somebody manually clicking a button. Job queues, scheduled reports, automated imports, approval flows, notifications, and background integrations can be easy to overlook because they are quiet when they work.
Use representative user accounts rather than testing everything as an administrator. Confirm that the people who should be able to perform a task still can, and that people who should not have access do not gain it accidentally.
4. Validate reporting outside Business Central too
The application can be healthy while the reporting layer is broken. Test Excel connections, Power BI models, exports, custom reports, financial statements, and any downstream data process that leaders rely on.
Do not stop at whether the report refreshes. Compare totals, filters, dimensions, dates, and key business measures against a known baseline. A refresh that succeeds with the wrong answer is still a failed test.
5. Test performance and the ugly edge cases
Small clean test transactions do not always expose real operational friction. Use realistic order sizes, item counts, dimensions, production structures, history, and integration volume where possible.
Also test the awkward cases users tend to remember: partial shipments, corrections, credits, reopens, failed approvals, late receipts, inventory shortages, and records that have already passed through several process steps.
Record evidence, not just opinions
A simple test log should capture the scenario, tester, expected result, actual result, evidence, issue severity, owner, and retest status. That gives the team a clear way to distinguish a true update blocker from a training question or a pre-existing problem.
If testing uncovers a significant Business Central problem that is difficult to isolate, the Free Business Central Rescue Review is available for one qualified unresolved issue. The goal is to help identify the most practical next step without requiring a partner change.
Do not wait until the production update window
The value of a preview environment is time. It gives the business room to find an issue, decide whether it is a Microsoft issue, an extension issue, an integration issue, a configuration issue, or a process issue, and then retest the correction before production is under pressure.
A short, disciplined testing plan is more useful than a long checklist nobody owns. Pick the workflows that matter, assign accountable testers, capture evidence, and resolve the highest-risk failures first.
Need help building a Business Central update test plan?
triniT Partners can help review your Business Central environment, prioritize the workflows that deserve testing, and work through issues found before a major update reaches production.
Comments