BC 2026 Wave 1 - what's actually changing in Manufacturing Microsoft published the 2026 Wave 1 release plan in March, with production rollout starting on the 1st of April. This is version 28. For partners and consultants working in the manufacturing module, this wave is more interesting than most - two significant changes plus a handful of smaller improvements worth knowing about. Quality Management - finally native The headline change. Until now, BC has not had a proper out-of-the-box quality management capability, which meant most manufacturing clients either bought an ISV add-on or had something custom built. Wave 1 introduces a native Quality Management extension that closes this gap. The extension installs automatically on new environments. For upgraded environments, it's available from AppSource. Public preview ran from November 2025, so it has had a few months of beta testing before going GA in April. Inspections can be triggered at four points: Purchase Receipt...
Posts
How to Use the Business Central MCP Server to Automate Your Shop Floor
Introduction Business Central have a lot of data about manufacturing operations - production orders, capacity, routings, quality, everything is there. The problem is that to get useful information out of it, you need to know exactly where to look. Which page, which filter, which report. For users that are not BC experts this is not easy. The MCP Server for Business Central, released in BC 27.1 (2025 Wave 2), change this situation. MCP stands for Model Context Protocol and it allow AI agents to connect directly to BC and query the data using natural language. Instead of navigate to a page and set filters, the user just type a question and the agent find the answer. This article explain how MCP work in practice for manufacturing scenarios. The focus is on what API pages you need to build in AL to expose production data to an AI agent, and what kind of actions the agent can perform. Pseudocode is used throughout to keep the focus on the logic rather than th...
Controlling Field Visibility on Master Pages Using User Setup in Business Central Overview In Microsoft Dynamics 365 Business Central, permissions alone are often insufficient when the requirement is to allow users to work with master data while hiding sensitive financial information such as balances, net changes, or internal values. Typical examples include: Users posting journals but not seeing G/L balances Users selecting bank accounts without seeing bank balances Users accessing master records but not financial KPIs This article describes a scalable and maintainable AL pattern that uses User Setup and page extensions to control field visibility at runtime. Design Principles This solution is based on the following principles: User-based configuration (not role-based) Centralized logic for visibility rules Reusable procedures SaaS-safe customization Minimal impact on permissions High-Level Archi...