Dynamics Business Central / NAV Developer Digest - Vol. 536

ArcherPoint’s Developer Digest focuses on Microsoft Dynamics 365 Business Central and Dynamics NAV development. This week’s volume includes what’s coming in Business Central 2025 wave 2 (v27), finding the root cause of a client crash, and using JSON to prompt AI.

The Dynamics 365 Business Central community, consisting of developers, project managers, and consultants, collaborates across various platforms to share valuable insights. At ArcherPoint, we greatly value their dedication and expertise. To ensure widespread access to this technical knowledge, we created Developer Digest.

What’s coming in Dynamics 365 Business Central 2025 wave 2 (v27)?

The next release of Business Central is right around the corner. Microsoft has announced the new features it intends to roll out from October 2025 through March 2026.

Some of the new features include:

• Use Sales Order Agent to automate sales order-taking
• Use enhanced chat with Copilot
• Use the E-Documents framework with Power Automate and other solutions
• Extend Copilot autofill using AL
• Print the Audit Trail report
• Evaluate quality of incoming goods and materials

You can see all the new features from Microsoft on their website, in What’s new and planned for Dynamics 365 Business Central 2025 wave 2 (v27).

In addition, Microsoft MVPs are weighing in on the new release:

Stefano Demiliani discusses the new Truncate table data with new AL method in his blog, Dynamics 365 Business Central: finally we’ll have TRUNCATE table in SaaS.

Erik Hougaard has a video that walks through all the new features in his video, What’s planned for 2025 Wave 2, BC27.

And Saurav Dhyani talks about the new features in his video, What’s New and Planned for Dynamics 365 Business Central.

Finding the root cause of a client crash

When a client crashes following an upgrade, there are some things that work…and some that don’t.

For instance, the online version of Business Central does not have access to Event Viewer in the Application Log.

One reliable technique is to use Telemetry using the timestamp and the operation ID, then locate the session_id.

Duilio Tacconi explains how he uncovered the problem of a customer site crashing after upgrading to 26.1 from 25.5.

Read his blog, Client Crash? Check Error Dialog signal, to learn what he found.

Not getting the best answer from AI? Might be how you ask the question!

Natural language prompts are convenient, but are they always the best way to elicit AI responses?

Stefano Demiliani answers this question with a qualified “NO!”

In his words, “LLMs don’t ‘understand’ language the way we do, but they follow patterns and structure. JSON is a structured format that leaves no ambiguity to LLMs (they don’t have to guess what you mean, but you’re telling them exactly what you want).”

In other words, since LLMs are trained in computer languages, they respond well when prompts are written in a form they readily “understand”, such as JSON, XML, or YAML.

While prompting with JSON might give you more consistent responses, there are times when natural language prompts are preferable and yield better results.

Read his blog, JSON prompting in AI: why?, for an interesting discussion on this topic.

Are you interested in Dynamics NAV and Business Central development? Check out our collection of NAV/BC Development Blogs.

Read “How To” blogs from ArcherPoint by Cherry Bekaert for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.

Trending Posts