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

Codeunit 9013 "User Login Time Tracker Impl."

System Application · System.Security.User

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 9026 "User Login Time Tracker" (calls, 7 links)User Login Time Tracker

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

Properties

Property Value
Access Internal
Permissions tabledata “User Login” = rim, tabledata “User Environment Login” = ri

Procedures

  • IsFirstLogin(UserSecurityID: Guid): Boolean
  • AnyUserLoggedInSinceDate(FromDate: Date): Boolean
  • UserLoggedInSinceDateTime(FromDateTime: DateTime): Boolean
  • UserLoggedInEnvironment(UserSecurityID: Guid): Boolean
  • GetPenultimateLoginDateTime(UserSecurityId: Guid): DateTime
  • CreateEnvironmentLoginInfo()
  • CreateOrUpdateLoginInfo()

Called by

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 9026 “User Login Time Tracker” (7 calls: AnyUserLoggedInSinceDate → AnyUserLoggedInSinceDate, CreateEnvironmentLoginInfo → CreateEnvironmentLoginInfo, CreateOrUpdateLoginInfo → CreateOrUpdateLoginInfo, …)

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: "codeunit", object_name: "User Login Time Tracker Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources