What's New: Key Updates in Learning Content (docs) for Systems Architects and Integration Developers
Walkthrough of the new Business Central integration documentation and its landing page (aka.ms/bc-integration). It covers Microsoft 365 apps, Power Platform, Dynamics products and Dataverse, Azure services, Microsoft Entra, infrastructure services and web services, with REST APIs as the recommended web service method.
- Introduction and Overview
- Integration Overview and Documentation Structure
- New Integration Landing Page and Navigation
- Microsoft 365, Office Apps, and Power Platform Integrations
- Dynamics Products, Dataverse, and Azure Services Integrations
- Microsoft Entra, Infrastructure Services, and Web Services
- Key Takeaways and Documentation Best Practices
- Related Sessions and Resources
Overview
The video shows new guidance in Business Central docs on integrations to and from Business Central. The material is meant to explain how integrations work, what is possible, and how to troubleshoot problems. A new landing page at aka.ms/bc-integration gives an overview and links to detailed articles for each integration class.
The walkthrough goes through Microsoft 365 and Office apps, Power Platform, Dynamics products and Dataverse, Azure services, Microsoft Entra and infrastructure services, and web services. It ends with advice to start learning in docs and to submit a pull request when you know something that is missing.
Key points
- The integration landing page is at aka.ms/bc-integration and links to articles for each integration class.
- The docs aim to explain how integrations work and how to troubleshoot them, not why to choose them.
- Power Platform integration relies mainly on REST APIs through the Power Platform connector.
- Dynamics products and Dataverse docs cover connectors, data synchronization, virtualization, change events and new business events.
- Azure integrations include Application Insights telemetry, Blob and File services and Azure Functions, supported by the HTTP client data type in AL and system modules that wrap Azure APIs.
- Web services offer three methods: REST APIs (recommended), and OData and SOAP as legacy methods.
- Microsoft Entra, Universal Print and network restriction with security service tags are covered; Microsoft Purview for audit is described as upcoming.
Features
Every feature below: status not stated, demoed.
| Feature | At |
|---|---|
| Integration Overview Documentation | 0:31 |
| New Integration Landing Page (aka.ms/bc-integration) | 3:03 |
| Microsoft 365 and Office Apps Integration Documentation | 4:02 |
| Power Platform Integration Documentation | 4:37 |
| Dynamics Products and Dataverse Integration Documentation | 5:10 |
| Azure Services Integration Support | 5:49 |
| Microsoft Entra and Infrastructure Services Documentation | 6:30 |
| Network Access Restriction with Security Service Tags | 7:04 |
| Web Services Documentation Update | 7:25 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
Not found in BC28-30: page “Connect apps”.
Quotes
- 0:31 “in this video I will show you some new guidance or documentation around Integrations to and from business Central”
- 0:51 “this piece of documentation or guidance is here for you to understand how Integrations work not necessarily why”
- 1:21 “understand first of all what’s possible and also how to troubleshoot this should you encounter any issues”
- 3:03 “there’s a new landing page called aka.ms slbc integration let’s take a look and uh see how how it”
- 7:25 “business Central supports three different ways to integrate to web services rest apis which is what you should use”
- 8:29 “whenever you start something new try to go to docs and start your learning”
- 8:49 “if you’re an expert on something and you know this is not in docs then do a a pull request and help others”
Disclaimers in the video
- 6:44 coming-later: upcoming also Microsoft purview for audit uh purposes or audit functionality