Business Central v29 Updates: Beyond the Release Plan

Your ERP team needs clear answers before each update. What will change? Who should test it? Will it affect daily work? For years, Microsoft’s release plans helped teams answer these questions. They grouped planned features into two release waves. Now, the way you track Business Central updates is changing. Microsoft has moved new roadmap content to its AI at Work roadmap. New release plans stopped publishing in September 2026. Older plans remain available for reference. So, your team needs a fresh way to watch changes. However, this does not mean every feature arrives without warning. It also does not mean major upgrade cycles have disappeared. The main change concerns how Microsoft shares its plans. Your testing process should reflect that change without losing its structure.

What Are Business Central Updates?

Business Central updates are changes to Microsoft’s ERP software. They can add features, improve tools, and change how users work. The AI at Work roadmap shows planned and released capabilities. It provides feature descriptions and estimated release dates. Those dates can change. Think of the roadmap as a live planning tool. Use it to find upcoming changes. Then, check Microsoft Learn for setup details and release guidance.

What changed in September?

Microsoft stopped publishing new release plans in September 2026. Its Release Planner no longer receives updates. That tool retires by November 15, 2026.

This does not mean all old guides have vanished.

Existing release plans remain available for historical reference. Also, Microsoft Learn continues as Microsoft’s documentation platform.

The old web plans were not fully static, either. Microsoft updated them weekly. Downloaded PDFs could still become outdated after teams saved them.

Now, Microsoft publishes new capabilities as it commits to them. Teams no longer need to wait for a twice-yearly announcement.

Did the release schedule change?

Not because of this roadmap move.

Microsoft states that established product release schedules will continue. The change affects roadmap publishing, not how products get built or deployed.

Business Central version 29 still starts the 2026 second release wave. Existing online customers receive an update notice. They can schedule the update within its five month window. That window ends in February 2027.

So, keep your major upgrade plan.

Also, add regular roadmap reviews between those larger planning sessions.

Common Problems Businesses Face

A live roadmap can help teams see changes sooner.

However, it can also create confusion without clear ownership.

Old plans stay in use

A project manager may rely on an old PDF. Meanwhile, a product owner may see newer roadmap details.

Both people may believe their source is current.

Replace old planning bookmarks with the current roadmap. Keep older guides only for historical context.

Preview looks like production

A feature announcement does not always mean production readiness.

For example, version 29 lists Microsoft Copilot chat as public preview. It lists several agent management features as generally available.

Teams must track those states separately.

A preview test should not become an automatic production approval.

Small changes escape testing

Teams often focus on large upgrades.

However, a small layout change can affect customer invoices. A permission change can affect who reviews an agent’s work.

So, assess business impact before deciding test effort.

Nobody owns the decision

IT may track the roadmap. Finance may own the affected process. Power users may understand the real risks.

Without a named owner, useful features sit unused.

Assign one process owner to each change. That person should coordinate testing and business approval.

How Business Central Updates Help

Version 29 adds useful changes for reports, audit visibility, and agents. Microsoft’s Business Central update 29.0 documentation provides the official feature list.

Modular Word document layouts

Composite Document Layouts bring a modular approach to Word reports. Related version 29 features include reusable headers, footers, and report themes.learn.microsoft+1

Instead of treating every document as a separate design, teams can reuse parts.

Think about invoices, quotes, and order confirmations.

These documents may need the same logo and footer. However, each needs its own main content.

Shared layout parts can reduce repeated design work. They can also help teams keep customer documents consistent.

Version 29 includes updated Word tools for these layout components. It also adds conditional visibility controls.

However, do not assume the new experience starts automatically. Microsoft lists “New Document Report Experience” as an optional feature. It is disabled by default in version 29.

Before enabling it, test:

• Company names, logos, and contact details.

• Page breaks on long documents.

• Headers and footers across document types.

• Tax details and payment terms.

• PDF output and emailed attachments.

• Custom fields from installed apps.

Clearer record ownership

Business Central already stores system fields for record creation and changes. Version 29 adds four system Flow Fields that show related usernames.

These fields are:

• SystemCreatedByUserName

• SystemCreatedByFullName

• SystemModifiedByUserName

• SystemModifiedByFullName

They complement existing user ID fields. They help teams see who created or last changed a record.

Also, version 29 supports system audit fields in analysis mode and profiles. This gives teams more ways to review record ownership.

For example, a business analyst could review recently changed vendor records.

However, these fields do not explain every change. They show creation and latest modification details. Treat them as useful context, not a complete change history.learn.microsoft+1

Expanded Copilot and agent tools

Version 29 includes easier agent permission management. It also adds a dedicated task pane for agent tasks. Users can review agent generated content directly on pages.

Payables Agent also gains improved purchase order matching. Meanwhile, Microsoft Copilot chat remains listed as public preview.

These differences matter when planning adoption.

Start with one clear task. Then, test the result and review process.

Ask practical questions:

• Can the agent access only the records it needs?

• Can users review its work before the next step?

• What happens when information is missing?

• Who handles failed or unclear tasks?

• Does the output match your business rules?

An agent should have a named business owner.

Also, users should know when to stop and request help.

Key Benefits

A steady review process can help your team:

• Find relevant changes before an upgrade deadline.

• Spend less time reading unrelated feature news.

• Separate preview tests from production decisions.

• Reuse document designs across key reports.

• Review record ownership more easily.

• Give agents clear permissions and review rules.

• Build a repeatable test process.

• Keep users informed through shorter training sessions.

These benefits depend on preparation.

The roadmap shows what may change. Your team decides how to manage that change.

Build a steady review cycle

Use this suggested cycle as a starting point.

1. Review roadmap changes each week.

2. Record relevant items in one shared tracker.

3. Assess business impact each month.

4. Test available features in a sandbox.

5. Approve production changes through your normal process.

6. Train users before they need the new tools.

7. Review results after the change.

Keep each tracker entry simple.

Record the feature name, roadmap ID, status, and review date. Also, name the process owner and test lead.

Include the target environment, key risks, and approval result.

Match tests to risk

Not every feature needs the same effort.

A display change may need a short user check. A payment or posting change needs deeper testing.

For higher risk changes, test the full process.

For example, test order entry through payment collection. Include reports, connected apps, and failed transaction cases.

Keep a stable sandbox for regular testing. Use a separate environment for experiments when practical.

Also, document how to disable optional features when possible. Do not assume you can reverse every production change.

A Practical Business Scenario

Consider a fictional distributor with offices in three states. Its finance team uses custom Word invoices. Its buyers want to test Payables Agent. The company once reviewed new features twice each year. Now, it adds a weekly roadmap check. A business analyst finds the version 29 layout changes. The product owner assigns finance as the process owner. First, finance tests a shared header and footer. Then, power users print short and long invoices. They check addresses, tax details, and payment terms. Next, purchasing tests agent matching with several sample orders. The team includes missing data and mismatched quantities. Meanwhile, the project manager records issues and approval decisions. The team does not enable every feature at once. Instead, it approves each change when the tests support it. This scenario shows a practical goal: smaller review steps, with clear control.

Why United States Businesses Care

Businesses across the United States may serve several regions. They may operate multiple warehouses, stores, or legal companies. That creates a need for consistent processes. However, local teams may use different documents and workflows. Your update plan should cover both shared rules and local needs.

National business challenges

For a business operating across several states, test:

• Customer documents for each legal company.

• Tax details used in each tested sales process.

• Warehouse workflows at different locations.

• Payment tools and connected applications.

• User permissions across teams.

• Training access across time zones.

Also, choose test users from more than one location. A process that works at headquarters may fail elsewhere. For example, one warehouse may use a connected shipping tool. Another may follow a different picking process. A Business Central partner in the United States can help coordinate this work. The goal is one clear plan, with room for local needs. Do not build separate update rules for every office. Instead, use shared approval standards and location specific test cases.

Frequently Asked Questions

What is the AI at Work roadmap?

It is Microsoft’s live roadmap for upcoming and released capabilities. It includes feature descriptions and estimated release dates.

Are Business Central release plans gone?

Microsoft stopped publishing new release plans in September 2026. Existing plans remain available for historical reference.

Did Microsoft end major updates?

No, the roadmap change does not replace established release schedules. Business Central version 29 still has a defined online update window.

What are Composite Document Layouts?

They bring a modular approach to Word document layouts. Related version 29 tools support reusable headers, footers, and report themes.

What does SystemCreatedByUserName show?

It shows the username linked to the record’s creator. Version 29 adds related fields for full names and latest modifiers

Are all version 29 AI features ready?

No, availability differs by feature. Microsoft lists Copilot chat as preview and several agent tools as generally available.

How often should we review updates?

Start with weekly roadmap checks and monthly impact reviews. Adjust that suggested cycle to your team’s size and business risks.

Should we test every new feature?

Assess each relevant feature, then match testing to its risk. Focus deeper tests on posting, payments, permissions, documents, and connected apps.

How Navisiontech Can Help

Your team needs more than a list of new features. It needs clear priorities, test owners, and a safe adoption plan. Navisiontech provides Business Central implementation, support, and integration services. Its solutions cover distribution, manufacturing, grocery, and specialty retail. Use Business Central support to discuss update readiness and ongoing assistance. Navisiontech also offers system upgrades and ongoing optimization through its support team. Include installed add ons in your testing plan. For example, check document access when using EasyLinks. Also, test payment workflows when using EasyEFT. These tools support document storage and credit card processing. Bring your current version, app list, and main pain points. Then, discuss which changes deserve attention first.

Book a free ERP assessment with Navisiontech. Request a focused review of your update readiness, testing needs, and next steps.