{"title":"Analyzing permission dependency cycle trace telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-permission-dependency-cycle-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-permission-dependency-cycle-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-permission-dependency-cycle-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 permission dependency cycle telemetry in Business Central to identify circular permission set references and investigate the dependency path.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing permission dependency cycle trace telemetry","slug":"analyzing-permission-dependency-cycle-trace-telemetry","at":0,"chars":2908},{"level":2,"title":"Dependency cycle discovered in permission sets","slug":"dependency-cycle-discovered-in-permission-sets","at":788,"chars":1843},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":943,"chars":126},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":1069,"chars":1562},{"level":2,"title":"Related information","slug":"related-information","at":2631,"chars":277}],"text":"# Analyzing permission dependency cycle trace telemetry\n> APPLIES TO: Business Central 2022 release wave 1 and later\nA permission dependency cycle occurs when a permission set depends on itself, which can happen when you build permission sets that include other permission sets. For example, suppose you create a permission set Y that includes permission set X. If you then try to modify permission set X to include permission set Y, you create a dependency cycle. When you create a permission dependency cycle in the Business Central client, you get an error similar to the following message:\nThe permission set [XX] has a circular reference on path [XX]->[YY]->[XX].\nThis telemetry data lets you identify and analyze permission problems that users might experience in Business Central.\n## Dependency cycle discovered in permission sets\nOccurs when a permission set dependency cycle is logged while permission sets are expanded or validated.\n### General dimensions\nDimension|Description or value\nmessage|Dependency cycle discovered in permission sets.\nseverityLevel|3\n### Custom dimensions\nDimension|Description or value\neventId|RT0032\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.\nalObjectId|Specifies the ID of the AL object in the current execution context. This value doesn't identify a permission set in the cycle.\nalObjectName|Specifies the name of the AL object in the current execution context.\nalObjectType|Specifies the type of the AL object in the current execution context.\nalStackTrace|The stack trace in AL.\nclientType|Specifies the type of client that opened the session, such as Background or Web. For a list of the client types, see ClientType Option Type<../developer/methods-auto/clienttype/clienttype-option>.\ncompanyName|The current company name.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|The version number of the component that emits telemetry (see the component dimension)\nenvironmentName|The name of the tenant environment. This dimension isn't included for Business Central on-premises environments. See Managing environments<tenant-admin-center-environments>.\nenvironmentType|The environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.\npermissionSetCycle|The dependency path of the permission sets in the cycle. Long paths are truncated in the middle to retain the start and end of the cycle.\ntelemetrySchemaVersion|The version of the Business Central telemetry schema.\n## Related information\nComposing Permission Sets<../developer/devenv-permissionset-composing>\n../developer/devenv-upgrading-extensions\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>"}