What's New: Telemetry (2025 release wave 1)
Business Central 2025 release wave 1 telemetry: five new telemetry types covering financial reporting usage, financial reporting definition changes, client add-in exceptions, server-side certificate validation, and detection of deprecated SOAP calls to UI pages (event RT0053).
- Introduction - Five New Telemetry Types
- Accessing Telemetry Samples and Documentation
- Financial Reporting Usage Telemetry
- Financial Reporting Definition Changes Telemetry
- Client Add-ins Troubleshooting Telemetry
- Server-side Certificate Validation Telemetry
- Deprecated SOAP Protocol Detection Telemetry
Overview
The video walks through five telemetry types added in 2025 release wave 1, with a demo of each. Two cover financial reporting: who runs reports, and changes to row, column and report definitions. The others cover client add-in exceptions, certificate validation failures in the AL runtime, and calls to UI pages through SOAP web services.
The SOAP telemetry is meant to help find integrations that must stop using SOAP before it is turned off in a later release. Telemetry samples and documentation are available at aka.ms/bctelemetry.
Key points
- Financial reporting usage telemetry records when users run financial reports on screen or from the request page, including row and column definitions. It can support auditing of who runs reports.
- Financial reporting definition changes telemetry covers row, column and report definitions. It captures created, modified, deleted, copied, imported and exported events, including via configuration packages.
- Client add-in errors now appear in the exceptions table, with environment, company, app, object, add-in name, assembly, error message and stack trace from JavaScript errors. This was previously not tracked and focuses on iframe-based add-ins.
- Server-side certificate validation telemetry logs failures when the AL runtime validates a certificate on an HTTP client call. It includes the certificate, endpoint, HTTP method and failure reason.
- Event RT0053 detects calls to UI pages through deprecated SOAP web services. It shows which endpoint is called, not which integration calls it.
- SOAP web services on UI pages will stop working in a later release, so integrations using them need to be found and changed.
- Telemetry documentation is at aka.ms/bctelemetry.
Features
Every feature below: status not stated, demoed.
| Feature | At |
|---|---|
| Financial Reporting Usage Telemetry | 1:08 |
| Financial Reporting Definition Changes Telemetry | 2:49 |
| Client Add-ins Exception Telemetry | 4:47 |
| Server-side Certificate Validation Telemetry | 6:29 |
| Deprecated SOAP Protocol Detection | 7:31 |
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.
Quotes
- 0:06 “in this release wave we added five new types of telemetry”
- 1:28 “it might be that you have auditing needs for your company so that you need to know who is actually running a financial report”
- 4:47 “this is a blind spot or was a blind spot until now and uh but now you have telemetry on”
- 6:29 “the AL runtime is performing whenever you call from HTP client in Al call to an endpoint uh where the endpoint has a CER”
- 7:51 “these soap web services on UI PES by Microsoft this has been deprecated and therefore this will be kind of stop working in a”
- 8:42 “as always in anything related to Telemetry is documented here under aka.ms slbc Telemetry”
Disclaimers in the video
- 7:31 coming-later: these soap web services on UI PES by Microsoft this has been deprecated and therefore this will be kind of stop working in a in a later release