Table 9062 "User Security Status"
Base Application · System.Security.User
Across versions
- BC23present
- BC242 fields changed, 1 fields added
- BC252 fields changed
- BC262 fields changed, 2 fields removed
- BC27-30unchanged
Neighbourhood 7 connected objects and pages
Base Application · System.Security.User · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 9062 “User Security Activities” (1 Learn page), Page 9818 “User Security Status List” (1).
Properties
| Property | Value |
|---|---|
| Caption | User Security Status |
| DataClassification | CustomerContent |
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” |
| 2 | User Name Δ BC24 | Code[50] | Specifies the user’s name. If the user is required to present credentials when starting the client, this is the name that the user must present. via Page 9818 “User Security Status List” | FlowField: lookup(User.“User Name” where(“User Security ID” = field(“User Security ID”))) |
| 3 | Full Name Δ BC24 | Text[80] | Specifies the full name of the user. via Page 9818 “User Security Status List” | FlowField: lookup(User.“Full Name” where(“User Security ID” = field(“User Security ID”))) |
| 13 | Reviewed | Boolean | Specifies if an administrator has reviewed this new user. When a new user is created, this field is empty to indicate that the user must be set up. via Page 9818 “User Security Status List” | |
| 15 | Belongs to User Group Δ BC25 Δ BC26 | Boolean | — | obsolete Removed 25.0; #if not CLEANSCHEMA25; FlowField: exist(“User Group Member” where(“User Security ID” = field(“User Security ID”))) |
| 20 | Users - To review | Integer | Specifies new users who have not yet been reviewed by an administrator. via Page 9062 “User Security Activities” | FlowField: count(“User Security Status” where(Reviewed = const(false), “User Security ID” = filter(<> ‘{00000000-0000-0000-0000-000000000000}’))) |
| 22 | Users - Not Group Members Δ BC25 Δ BC26 | Integer | — | obsolete Removed 25.0; #if not CLEANSCHEMA25; FlowField: |
| 25 | CDS Integration Errors | Integer | Specifies the number of errors related to data integration. via Page 9062 “User Security Activities” | FlowField: count(“Integration Synch. Job Errors”) |
| 26 | Coupled Data Synch Errors | Integer | Specifies the number of errors that occurred in the latest synchronization of coupled data between Business Central and Dynamics 365 Sales. via Page 9062 “User Security Activities” | FlowField: count(“CRM Integration Record” where(Skipped = const(true))) |
| 27 | User Exists + BC24 | Boolean | — | FlowField: exist(User where(“User Security ID” = field(“User Security ID”))) |
Keys
- Key1: User Security ID (clustered)
- Key2: Reviewed
Procedures
KeepOnlyEnabledUsers()LoadUsers()LogUserReviewActivity()
Relations
- lookup page Page 9818 “User Security Status List”
- Coupled Data Synch Errors: CalcFormula Table 5331 “CRM Integration Record”
- CDS Integration Errors: CalcFormula Table 5339 “Integration Synch. Job Errors”
- Belongs to User Group: CalcFormula Table 9001 “User Group Member”
- Users - To review: CalcFormula Table 9062 “User Security Status”
Referenced by
1 fields in 1 objects relate to this table (TableRelation or CalcFormula).
- Table 9062 “User Security Status”: Users - To review
Pages and codeunits on this table
- Page 9062 “User Security Activities” (source table)
- Page 9818 “User Security Status List” (source 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 9843 “User Selection” (1 call:
LoadUsers → FilterSystemUserAndGroupUsers)
Deprecations
- field Belongs to User Group: Removed 25.0 (#if not CLEANSCHEMA25), “User group membership cannot be calculated via a flow field in the new user group system.”
- field Users - Not Group Members: Removed 25.0 (#if not CLEANSCHEMA25), “User group membership cannot be calculated via a flow field in the new user group system.”
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). 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: "User Security Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.