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

Table 9018 "Custom Permission Set In Plan"

System Application · System.Azure.Identity

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Page 9058 "Custom Permission Set In Plan" (pages and codeunits on it)Custom Permission Set In PlanCodeunit 9822 "Plan Configuration Impl." (event subscribers, 3 links)Plan Configuration Impl.Codeunit 9825 "Plan Configuration" (calls, 4 links)Plan Configuration

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 “Custom Permissions In License” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Custom Permissions In License
Access Internal
Extensible false

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
1 Id Integer — AutoIncrement; DataClassification SystemMetadata
2 Plan ID Guid Specifies the ID of the license. via Page 9058 “Custom Permission Set In Plan” TableRelation Plan.“Plan ID”; DataClassification SystemMetadata
3 Role ID Code[20] Specifies the ID of the permission set that will be assigned to users with this license. via Page 9058 “Custom Permission Set In Plan” TableRelation “Aggregate Permission Set”.“Role ID”; DataClassification CustomerContent
4 Role Name Text[30] Specifies the description of the permission set. via Page 9058 “Custom Permission Set In Plan” FlowField: lookup(“Aggregate Permission Set”.Name where(“Role ID” = field(“Role ID”))); not editable
5 App ID Guid — DataClassification SystemMetadata
6 App Name Text[250] Specifies the name of the extension from which the permission set originates. via Page 9058 “Custom Permission Set In Plan” FlowField: lookup(“Published Application”.Name where(ID = field(“App ID”), “Tenant Visible” = const(true))); not editable
7 Scope Option — OptionCaption: System,Tenant; DataClassification SystemMetadata
8 Company Name Text[30] Specifies the name of the company that this permission set is limited to for this plan. via Page 9058 “Custom Permission Set In Plan” TableRelation Company; DataClassification SystemMetadata

Keys

  • PrimaryKey: Id (clustered)
  • UniqueKey: Plan ID, Role ID, Company Name, Scope, App ID

Trigger event subscribers

Triggers

OnInsert, OnDelete, OnModify, OnRename

Pages and codeunits on this table

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

  • Codeunit 9825 “Plan Configuration” (4 calls: OnDelete → VerifyUserHasRequiredPermissionSet, OnInsert → VerifyUserHasRequiredPermissionSet, OnModify → VerifyUserHasRequiredPermissionSet, …)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Custom Permission Set In Plan"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources