Analyzing permission dependency cycle trace telemetry
APPLIES TO: Business Central 2022 release wave 1 and later
A permission dependency cycle occurs when a permission set depends on itself, which can happen when you build permissions sets that include other permission sets. For example, suppose you create a permission set Y that includes permission set X. If you then try 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:
The permission set [XX] has a circular reference on path [XX]->[YY]->[XX].
This telemetry data let's you identify and analyze permission problems that users might experience in Business Central.
Dependency cycle discovered in permission sets
Occurs when there's permission set dependency cycle in the application.
General dimensions
Dimension | Description or value |
---|---|
message | Dependency cycle discovered in permission sets |
severityLevel | 3 |
Custom dimensions
Dimension | Description or value |
---|---|
eventId | RT0032 |
aadTenantId |
Note Azure Active Directory is now Microsoft Entra ID. Learn more |
alObjectId | Specifies the ID of the object causing the dependency cycle. If there's no value or the value is 0, then the error wasn't related to a specific object, which typically happens when permissionArea is something other than Object . |
alObjectType | The type of the AL object that the user was trying to access, like a table or page. |
clientType | 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. |
companyName | The current company name. |
component | Dynamics 365 Business Central Server |
componentVersion | The version number of the component that emits telemetry (see the component dimension) |
environmentName | The name of the tenant environment. See Managing Environments. This dimension isn't included for Business Central on-premises environments. |
environmentType | The environment type for the tenant, such as Production, Sandbox, Trial. See Environment Types |
permissionArea | The area that the dependency cycle is related to. Possible values include: System , Entitlement , Company , Object . |
permissionType | The permission that the dependency cycle pertains to. Possible values: Delete , Execute , Insert , Modify , Read , Undefined |
telemetrySchemaVersion | The version of the Business Central telemetry schema. |
See also
Composing Permission Sets
Upgrading Extensions
Monitoring and Analyzing Telemetry
Enable Sending Telemetry to Application Insights
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for