BC Observatoryunofficial, made by waldo
tableAdministration & Setupofficial - Microsoftderived - from the source, no model textobsolete - removed

Table 9007 "User Group Plan"

Base Application · System.Security.AccessControl

Open in Claude9007.mdSource on GitHub

Across versionsobsolete removed since 25.0

  1. BC23present
  2. BC243 fields changed
  3. BC25declaration changed
  4. BC26declaration changed
  5. BC27-30unchanged

Neighbourhood 1 connected objects and pages

Table 9000 "User Group" (relates to, 2 links)User Group

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 User Group Plan
DataClassification CustomerContent
ObsoleteState Removed
ObsoleteTag 25.0
ObsoleteReason [220_UserGroups] The user groups functionality is deprecated. Default permission sets per plan are defined using the Plan Configuration codeunit. To learn more, go to https://go.microsoft.com/fwlink/?linkid=2245709.

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 Plan ID Δ BC24 Guid — TableRelation System.Azure.Identity.Plan.“Plan ID”
2 User Group Code Code[20] — TableRelation Table 9000 “User Group” (“User Group”.Code)
10 Plan Name Δ BC24 Text[50] — FlowField: lookup(System.Azure.Identity.Plan.Name where(“Plan ID” = field(“Plan ID”)))
11 User Group Name Δ BC24 Text[50] — FlowField: lookup(“User Group”.Name where(Code = field(“User Group Code”)))

Keys

  • Key1: Plan ID, User Group Code (clustered)

Relations

Deprecations

  • object: Removed 25.0 (#if not CLEANSCHEMA25), “[220_UserGroups] The user groups functionality is deprecated. Default permission sets per plan are defined using the Plan Configuration codeunit. To learn more, go to https://go.microsoft.com/fwlink/?linkid=2245709.”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 1 sources