tableAdministration & Setupofficial - Microsoftderived - from the source, no model text

Table 9802 "Permission Set Link"

Base Application · System.Security.AccessControl

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 3 connected objects and pages

Page 9846 "Changed Permission Set List" (pages and codeunits on it)Changed Permission Set ListCodeunit 1351 "Telemetry Subscribers" (event subscribers, 2 links)Telemetry SubscribersCodeunit 9002 "Permission Manager" (calls, 2 links)Permission Manager

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.

Base Application · System.Security.AccessControl · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Permission Set Link
DataClassification CustomerContent
Permissions TableData “Permission Set Link” = rmd

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 Permission Set ID Code[20] — TableRelation “Permission Set”.“Role ID”; DataClassification SystemMetadata
2 Linked Permission Set ID Code[20] — TableRelation “Tenant Permission Set”.“Role ID”; DataClassification SystemMetadata
3 Source Hash Text[250] — DataClassification SystemMetadata

Keys

  • Key1: Permission Set ID, Linked Permission Set ID (clustered)

Trigger event subscribers

Procedures

  • SourceHashHasChanged(): Boolean
  • MarkWithChangedSource()
  • GetSourceForLinkedPermissionSet(LinkedPermissionSetId: Code[20]): Code[20]

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.

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: "Permission Set Link"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources