# Analyzing report layout lifecycle telemetry
> APPLIES TO: Business Central 2024 release wave 2 (v25) and later.
This article describes the telemetry gathered for actions taken by users on report layouts. See Get started with report layouts</ui-get-started-layouts?tabs=copy#get-started>.
These events use normal verbosity (severityLevel 1) and `TelemetryScope::All`.
## Report layout added by user
Occurs when a user adds a new report layout.
### General dimensions
The following table explains the general dimensions of this trace.
Dimension|Description or value
message|Report layout added by user
user_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
Dimension|Description or value
aadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.
alAction|New
alLayoutDescription|Specifies the description supplied for the new layout.
alExcelConfiguration|Specifies the Excel sheet configuration recorded for the layout.
alLayoutFormat|Specifies the layout file type. Possible values: RDLC (.rdlc file type), Word (.docx file type), Excel (.xlsx file type), Custom (custom file type, indicated as External in the client UI).
alLayoutName|Specifies the name of the report layout.
alReportId|Specifies the ID of the report assigned the layout.
companyName|The current company name.
environmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.
environmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.
eventId|AL0000N0E
### Sample KQL code (report layout added)
This KQL code can help you get started analyzing which report layouts users add:
```kql
traces
| where timestamp > ago(60d) // adjust as needed
| where customDimensions has 'AL0000N0E' // performance optimization
| where customDimensions.eventId == 'AL0000N0E'
| project timestamp
// in which environment/company did it happen
, aadTenantId = customDimensions.aadTenantId
, environmentName = customDimensions.environmentName
, environmentType = customDimensions.environmentType
, companyName = customDimensions.companyName
// for which report and layout
, reportId = customDimensions.alReportId // object ID of the report
, layoutName = customDimensions.alLayoutName
, layoutFormat = customDimensions.alLayoutFormat // possible values: RDLC, Word, Excel, Custom
// what did the user do
, action = customDimensions.alAction // alAction is "New" for this event
// user who performed the action
, user_Id // user telemetry ID
```
## Report layout default changed by user
Occurs when a user changes the default layout used by a report.
### General dimensions
The following table explains the general dimensions of this trace.
Dimension|Description or value
message|Report layout default changed by user
user_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
Dimension|Description or value
aadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.
alAction|SetDefault
alLayoutFormat|In versions that emit this dimension, specifies the layout file type. Before version 25.1, the value is an integer. The current default-change event doesn't emit this dimension.
alLayoutName|Specifies the name of the report layout.
alReportId|Specifies the ID of the report assigned the layout.
companyName|The current company name.
environmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.
environmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.
eventId|AL0000N0D
### Sample KQL code (report layout default changed)
This KQL code can help you get started analyzing which report layouts users select as defaults:
```kql
traces
| where timestamp > ago(60d) // adjust as needed
| where customDimensions has 'AL0000N0D' // performance optimization
| where customDimensions.eventId == 'AL0000N0D'
| project timestamp
// in which environment/company did it happen
, aadTenantId = customDimensions.aadTenantId
, environmentName = customDimensions.environmentName
, environmentType = customDimensions.environmentType
, companyName = customDimensions.companyName
// for which report and layout
, reportId = customDimensions.alReportId // object ID of the report
, newDefaultLayoutName = customDimensions.alLayoutName
// NB! alLayoutFormat shows as an integer in the telemetry in versions prior to 25.1
// The current default-change event doesn't emit alLayoutFormat.
, layoutFormat = customDimensions.alLayoutFormat // possible values: RDLC, Word, Excel, Custom
// what did the user do
, action = customDimensions.alAction // alAction is "SetDefault" for this event
// user who performed the action
, user_Id // user telemetry ID
```
## Report layout properties changed by user
Occurs when a user changes the properties of a user-defined layout or creates a copy through the layout properties dialog.
### General dimensions
The following table explains the general dimensions of this trace.
Dimension|Description or value
message|Report layout properties changed by user
user_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
Dimension|Description or value
aadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.
alAction|Edit
alOldLayoutDescription|Specifies the layout description recorded in the old-value dimension. The value is captured after the layout is updated and can match alNewLayoutDescription.
alOldLayoutName|Specifies the layout name recorded in the old-value dimension. The value is captured after the layout is updated and can match alNewLayoutName.
alNewLayoutDescription|Specifies the new description of the layout.
alNewLayoutName|Specifies the new name of the layout.
alReportId|Specifies the ID of the report assigned the layout.
companyName|The current company name.
environmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.
environmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.
eventId|AL0000N0H
### Sample KQL code (report layout properties changed)
This KQL code can help you get started analyzing changes to report layout properties:
```kql
traces
| where timestamp > ago(60d) // adjust as needed
| where customDimensions has 'AL0000N0H' // performance optimization
| where customDimensions.eventId == 'AL0000N0H'
| project timestamp
// in which environment/company did it happen
, aadTenantId = customDimensions.aadTenantId
, environmentName = customDimensions.environmentName
, environmentType = customDimensions.environmentType
, companyName = customDimensions.companyName
// for which report
, reportId = customDimensions.alReportId // object ID of the report
// what did the user do
, action = customDimensions.alAction // alAction is "Edit" for this event
, oldLayoutDescription = customDimensions.alOldLayoutDescription
, oldLayoutName = customDimensions.alOldLayoutName
, newLayoutDescription = customDimensions.alNewLayoutDescription
, newLayoutName = customDimensions.alNewLayoutName
// user who performed the action
, user_Id // user telemetry ID
```
## Report layout exported by user
Occurs when a user exports a layout used by a report.
### General dimensions
The following table explains the general dimensions of this trace.
Dimension|Description or value
message|Report layout exported by user
user_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
Dimension|Description or value
aadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.
alAction|Export
alLayoutName|Specifies the name of the report layout.
alReportId|Specifies the ID of the report assigned the layout.
companyName|The current company name.
environmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.
environmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.
eventId|AL0000N0I
### Sample KQL code (report layout exported)
This KQL code can help you get started analyzing which report layouts users export:
```kql
//
traces
| where timestamp > ago(60d) // adjust as needed
| where customDimensions has 'AL0000N0I' // performance optimization
| where customDimensions.eventId == 'AL0000N0I'
| project timestamp
// in which environment/company did it happen
, aadTenantId = customDimensions.aadTenantId
, environmentName = customDimensions.environmentName
, environmentType = customDimensions.environmentType
, companyName = customDimensions.companyName
// for which report and layout
, reportId = customDimensions.alReportId // object ID of the report
, layoutName = customDimensions.alLayoutName
// what did the user do
, action = customDimensions.alAction // alAction is "Export" for this event
// user who performed the action
, user_Id // user telemetry ID
```
## Report layout deleted by user
Occurs when a user deletes a report layout.
### General dimensions
The following table explains the general dimensions of this trace.
Dimension|Description or value
message|Report layout deleted by user
user_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
Dimension|Description or value
aadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.
alAction|Delete
alLayoutName|Specifies the name of the report layout.
alReportId|Specifies the ID of the report assigned the layout.
companyName|The current company name.
environmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.
environmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.
eventId|AL0000N0F
### Sample KQL code (report layout deleted)
This KQL code can help you get started analyzing which report layouts users delete:
```kql
traces
| where timestamp > ago(60d) // adjust as needed
| where customDimensions has 'AL0000N0F' // performance optimization
| where customDimensions.eventId == 'AL0000N0F'
| project timestamp
// in which environment/company did it happen
, aadTenantId = customDimensions.aadTenantId
, environmentName = customDimensions.environmentName
, environmentType = customDimensions.environmentType
, companyName = customDimensions.companyName
// for which report and layout
, reportId = customDimensions.alReportId // object ID of the report
, layoutName = customDimensions.alLayoutName
// what did the user do
, action = customDimensions.alAction // alAction is "Delete" for this event
// user who performed the action
, user_Id // user telemetry ID
```
## Report layout replaced by user
Occurs when a user replaces a report layout with another layout.
### General dimensions
The following table explains the general dimensions of this trace.
Dimension|Description or value
message|Report layout replaced by user
user_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
Dimension|Description or value
aadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.
alAction|Replace
alLayoutDescription|Specifies the description supplied for the replacement layout.
alLayoutFormat|Specifies the replacement layout format. Possible values include RDLC, Word, Excel, and Custom.
alLayoutName|Specifies the name of the report layout.
alReportId|Specifies the ID of the report assigned the layout.
companyName|The current company name.
environmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.
environmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.
eventId|AL0000N0G
### Sample KQL code (report layout replaced)
This KQL code can help you get started analyzing which report layouts users replace:
```kql
traces
| where timestamp > ago(60d) // adjust as needed
| where customDimensions has 'AL0000N0G' // performance optimization
| where customDimensions.eventId == 'AL0000N0G'
| project timestamp
// in which environment/company did it happen
, aadTenantId = customDimensions.aadTenantId
, environmentName = customDimensions.environmentName
, environmentType = customDimensions.environmentType
, companyName = customDimensions.companyName
// for which report and layout
, reportId = customDimensions.alReportId // object ID of the report
, layoutName = customDimensions.alLayoutName
// what did the user do
, action = customDimensions.alAction // alAction is "Replace" for this event
// user who performed the action
, user_Id // user telemetry ID
```
## Related information
../developer/devenv-report-performance
Troubleshooting report errors<../developer/devenv-reports-troubleshooting>
Monitoring and Analyzing Telemetry<telemetry-overview>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-report-layout-lifecycle-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-report-layout-lifecycle-trace/
