tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 9019 "Default Permission Set In Plan"

System Application · System.Azure.Identity

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Page 9827 "Default Permission Set In Plan" (pages and codeunits on it)Default Permission Set In Plan

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

System Application · System.Azure.Identity · captioned “Default Permissions in License” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Default Permissions in License
Access Internal

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
2 Plan ID Guid — TableRelation Plan.“Plan ID”; DataClassification SystemMetadata
3 Role ID Code[20] Specifies the ID of the permission set. via Page 9827 “Default Permission Set In Plan” TableRelation “Aggregate Permission Set”.“Role ID”; DataClassification SystemMetadata
4 Role Name Text[30] Specifies the description of the permission set. via Page 9827 “Default Permission Set In Plan” FlowField: lookup(“Aggregate Permission Set”.Name where(“Role ID” = field(“Role ID”)))
5 App ID Guid — DataClassification SystemMetadata
6 App Name Text[250] Specifies the name of the extension that provides the permission set. via Page 9827 “Default Permission Set In Plan” FlowField: lookup(“Published Application”.Name where(ID = field(“App ID”), “Tenant Visible” = const(true)))
7 Scope Option Specifies the scope of the permission set. via Page 9827 “Default Permission Set In Plan” OptionCaption: System,Tenant; DataClassification SystemMetadata

Keys

  • UniqueKey: Plan ID, Role ID, Scope, App ID (clustered)

Pages and codeunits on this table

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Default Permission Set In Plan"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources