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

Table 9005 "User Plan"

System Application · System.Azure.Identity

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Table 9004 "Plan" (relates to)PlanPage 9822 "User Plan Members" (pages and codeunits on it)User Plan MembersPage 9823 "User Plan Members FactBox" (pages and codeunits on it)User Plan Members FactBoxPage 9826 "User Plans FactBox" (pages and codeunits on it)User Plans FactBox

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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption User Plan
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
1 User Security ID Guid — TableRelation User.“User Security ID”; DataClassification EndUserPseudonymousIdentifiers
2 Plan ID Guid — TableRelation Plan.“Plan ID”; DataClassification SystemMetadata
10 User Name Code[50] Specifies the short name for the user. via Page 9822 “User Plan Members” FlowField: lookup(User.“User Name” where(“User Security ID” = field(“User Security ID”)))
11 User Full Name Text[80] Specifies the full name of the user. via Page 9822 “User Plan Members” FlowField: lookup(User.“Full Name” where(“User Security ID” = field(“User Security ID”)))
12 Plan Name Text[50] Specifies the subscription plan. via Page 9822 “User Plan Members” FlowField: lookup(Plan.Name where(“Plan ID” = field(“Plan ID”)))

Keys

  • Key1: Plan ID, User Security ID (clustered)

Relations

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

Evidence 1 sources