{"title":"Analyzing report layout lifecycle telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-report-layout-lifecycle-trace/","by":"JOP-AL","license":"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.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-report-layout-lifecycle-trace","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Analyze report layout lifecycle telemetry in Business Central to track layouts added, replaced, deleted, exported, or selected as the report default.","date":"2026-11-17","meta":{"topic":"reference"},"outline":[{"level":1,"title":"Analyzing report layout lifecycle telemetry","slug":"analyzing-report-layout-lifecycle-telemetry","at":0,"chars":14666},{"level":2,"title":"Report layout added by user","slug":"report-layout-added-by-user","at":369,"chars":2482},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":445,"chars":372},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":817,"chars":1065},{"level":3,"title":"Sample KQL code (report layout added)","slug":"sample-kql-code-report-layout-added","at":1882,"chars":969},{"level":2,"title":"Report layout default changed by user","slug":"report-layout-default-changed-by-user","at":2851,"chars":2548},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":2956,"chars":382},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":3338,"chars":900},{"level":3,"title":"Sample KQL code (report layout default changed)","slug":"sample-kql-code-report-layout-default-changed","at":4238,"chars":1161},{"level":2,"title":"Report layout properties changed by user","slug":"report-layout-properties-changed-by-user","at":5399,"chars":2731},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":5566,"chars":385},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":5951,"chars":1110},{"level":3,"title":"Sample KQL code (report layout properties changed)","slug":"sample-kql-code-report-layout-properties-changed","at":7061,"chars":1069},{"level":2,"title":"Report layout exported by user","slug":"report-layout-exported-by-user","at":8130,"chars":2052},{"level":3,"title":"General dimensions","slug":"general-dimensions-3","at":8218,"chars":375},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-3","at":8593,"chars":703},{"level":3,"title":"Sample KQL code (report layout exported)","slug":"sample-kql-code-report-layout-exported","at":9296,"chars":886},{"level":2,"title":"Report layout deleted by user","slug":"report-layout-deleted-by-user","at":10182,"chars":2036},{"level":3,"title":"General dimensions","slug":"general-dimensions-4","at":10259,"chars":374},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-4","at":10633,"chars":703},{"level":3,"title":"Sample KQL code (report layout deleted)","slug":"sample-kql-code-report-layout-deleted","at":11336,"chars":882},{"level":2,"title":"Report layout replaced by user","slug":"report-layout-replaced-by-user","at":12218,"chars":2257},{"level":3,"title":"General dimensions","slug":"general-dimensions-5","at":12317,"chars":375},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-5","at":12692,"chars":898},{"level":3,"title":"Sample KQL code (report layout replaced)","slug":"sample-kql-code-report-layout-replaced","at":13590,"chars":885},{"level":2,"title":"Related information","slug":"related-information","at":14475,"chars":191}],"text":"# Analyzing report layout lifecycle telemetry\n> APPLIES TO: Business Central 2024 release wave 2 (v25) and later.\nThis 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>.\nThese events use normal verbosity (severityLevel 1) and `TelemetryScope::All`.\n## Report layout added by user\nOccurs when a user adds a new report layout.\n### General dimensions\nThe following table explains the general dimensions of this trace.\nDimension|Description or value\nmessage|Report layout added by user\nuser_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.\n### Custom dimensions\nDimension|Description or value\naadTenantId|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.\nalAction|New\nalLayoutDescription|Specifies the description supplied for the new layout.\nalExcelConfiguration|Specifies the Excel sheet configuration recorded for the layout.\nalLayoutFormat|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).\nalLayoutName|Specifies the name of the report layout.\nalReportId|Specifies the ID of the report assigned the layout.\ncompanyName|The current company name.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000N0E\n### Sample KQL code (report layout added)\nThis KQL code can help you get started analyzing which report layouts users add:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000N0E' // performance optimization\n| where customDimensions.eventId == 'AL0000N0E'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// for which report and layout\n, reportId = customDimensions.alReportId // object ID of the report\n, layoutName = customDimensions.alLayoutName\n, layoutFormat = customDimensions.alLayoutFormat // possible values: RDLC, Word, Excel, Custom\n// what did the user do\n, action = customDimensions.alAction // alAction is \"New\" for this event\n// user who performed the action\n, user_Id // user telemetry ID\n```\n## Report layout default changed by user\nOccurs when a user changes the default layout used by a report.\n### General dimensions\nThe following table explains the general dimensions of this trace.\nDimension|Description or value\nmessage|Report layout default changed by user\nuser_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.\n### Custom dimensions\nDimension|Description or value\naadTenantId|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.\nalAction|SetDefault\nalLayoutFormat|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.\nalLayoutName|Specifies the name of the report layout.\nalReportId|Specifies the ID of the report assigned the layout.\ncompanyName|The current company name.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000N0D\n### Sample KQL code (report layout default changed)\nThis KQL code can help you get started analyzing which report layouts users select as defaults:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000N0D' // performance optimization\n| where customDimensions.eventId == 'AL0000N0D'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// for which report and layout\n, reportId = customDimensions.alReportId // object ID of the report\n, newDefaultLayoutName = customDimensions.alLayoutName\n// NB! alLayoutFormat shows as an integer in the telemetry in versions prior to 25.1\n// The current default-change event doesn't emit alLayoutFormat.\n, layoutFormat = customDimensions.alLayoutFormat // possible values: RDLC, Word, Excel, Custom\n// what did the user do\n, action = customDimensions.alAction // alAction is \"SetDefault\" for this event\n// user who performed the action\n, user_Id // user telemetry ID\n```\n## Report layout properties changed by user\nOccurs when a user changes the properties of a user-defined layout or creates a copy through the layout properties dialog.\n### General dimensions\nThe following table explains the general dimensions of this trace.\nDimension|Description or value\nmessage|Report layout properties changed by user\nuser_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.\n### Custom dimensions\nDimension|Description or value\naadTenantId|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.\nalAction|Edit\nalOldLayoutDescription|Specifies the layout description recorded in the old-value dimension. The value is captured after the layout is updated and can match alNewLayoutDescription.\nalOldLayoutName|Specifies the layout name recorded in the old-value dimension. The value is captured after the layout is updated and can match alNewLayoutName.\nalNewLayoutDescription|Specifies the new description of the layout.\nalNewLayoutName|Specifies the new name of the layout.\nalReportId|Specifies the ID of the report assigned the layout.\ncompanyName|The current company name.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000N0H\n### Sample KQL code (report layout properties changed)\nThis KQL code can help you get started analyzing changes to report layout properties:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000N0H' // performance optimization\n| where customDimensions.eventId == 'AL0000N0H'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// for which report\n, reportId = customDimensions.alReportId // object ID of the report\n// what did the user do\n, action = customDimensions.alAction // alAction is \"Edit\" for this event\n, oldLayoutDescription = customDimensions.alOldLayoutDescription\n, oldLayoutName = customDimensions.alOldLayoutName\n, newLayoutDescription = customDimensions.alNewLayoutDescription\n, newLayoutName = customDimensions.alNewLayoutName\n// user who performed the action\n, user_Id // user telemetry ID\n```\n## Report layout exported by user\nOccurs when a user exports a layout used by a report.\n### General dimensions\nThe following table explains the general dimensions of this trace.\nDimension|Description or value\nmessage|Report layout exported by user\nuser_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.\n### Custom dimensions\nDimension|Description or value\naadTenantId|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.\nalAction|Export\nalLayoutName|Specifies the name of the report layout.\nalReportId|Specifies the ID of the report assigned the layout.\ncompanyName|The current company name.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000N0I\n### Sample KQL code (report layout exported)\nThis KQL code can help you get started analyzing which report layouts users export:\n```kql\n//\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000N0I' // performance optimization\n| where customDimensions.eventId == 'AL0000N0I'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// for which report and layout\n, reportId = customDimensions.alReportId // object ID of the report\n, layoutName = customDimensions.alLayoutName\n// what did the user do\n, action = customDimensions.alAction // alAction is \"Export\" for this event\n// user who performed the action\n, user_Id // user telemetry ID\n```\n## Report layout deleted by user\nOccurs when a user deletes a report layout.\n### General dimensions\nThe following table explains the general dimensions of this trace.\nDimension|Description or value\nmessage|Report layout deleted by user\nuser_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.\n### Custom dimensions\nDimension|Description or value\naadTenantId|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.\nalAction|Delete\nalLayoutName|Specifies the name of the report layout.\nalReportId|Specifies the ID of the report assigned the layout.\ncompanyName|The current company name.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000N0F\n### Sample KQL code (report layout deleted)\nThis KQL code can help you get started analyzing which report layouts users delete:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000N0F' // performance optimization\n| where customDimensions.eventId == 'AL0000N0F'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// for which report and layout\n, reportId = customDimensions.alReportId // object ID of the report\n, layoutName = customDimensions.alLayoutName\n// what did the user do\n, action = customDimensions.alAction // alAction is \"Delete\" for this event\n// user who performed the action\n, user_Id // user telemetry ID\n```\n## Report layout replaced by user\nOccurs when a user replaces a report layout with another layout.\n### General dimensions\nThe following table explains the general dimensions of this trace.\nDimension|Description or value\nmessage|Report layout replaced by user\nuser_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.\n### Custom dimensions\nDimension|Description or value\naadTenantId|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.\nalAction|Replace\nalLayoutDescription|Specifies the description supplied for the replacement layout.\nalLayoutFormat|Specifies the replacement layout format. Possible values include RDLC, Word, Excel, and Custom.\nalLayoutName|Specifies the name of the report layout.\nalReportId|Specifies the ID of the report assigned the layout.\ncompanyName|The current company name.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000N0G\n### Sample KQL code (report layout replaced)\nThis KQL code can help you get started analyzing which report layouts users replace:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000N0G' // performance optimization\n| where customDimensions.eventId == 'AL0000N0G'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// for which report and layout\n, reportId = customDimensions.alReportId // object ID of the report\n, layoutName = customDimensions.alLayoutName\n// what did the user do\n, action = customDimensions.alAction // alAction is \"Replace\" for this event\n// user who performed the action\n, user_Id // user telemetry ID\n```\n## Related information\n../developer/devenv-report-performance\nTroubleshooting report errors<../developer/devenv-reports-troubleshooting>\nMonitoring and Analyzing Telemetry<telemetry-overview>"}