From the Microsoft Dynamics 365 Business Central blogs: Send emails with report attachments; Per-tenant extensions; Understanding dimensions; Engineering

In this review of the Dynamics 365 Business Central blogs:

• Sending emails with report attachments via API
• MCP server for BC administration now supports handling PTEs
• Understanding how dimensions are use in BC
• Copilot and AL development: Transforming the future of BC engineering

Sending emails with report attachments via API in Business Central

Writing on the CloudFront blog, Vaishnavi Joshi stated that in many system integrations, outside applications need a way to tell Business Central to send documents by email. 

She noted that these documents can include sales order confirmations, invoices, or custom reports that must be delivered directly to customers.

Joshi wrote that using the D365BC API page that she showed in her blog post, you can create an endpoint that accepts a sales order number and a customer number. 

She pointed out that when the endpoint is called, D365BC first checks that both values are valid. After validation, it runs a custom codeunit called SendCustomerEmails that sends all required documents as email attachments.

Joshi explained that this setup makes it possible for external applications, such as ERP integrations, e-commerce platforms, or automation tools, to call D365BC and trigger document delivery automatically, without requiring any manual action from a user.

My MCP server for Dynamics 365 Business Central administration now supports handling PTEs

On his blog, Stefano Demiliani wrote that over the past few weeks, one of the most common questions from users of his Model Context Protocol (MCP) server for D365BC administration (code-named YAMPI) has been whether it can also handle per-tenant extensions (PTEs).