BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 5513 "Graph Mgt - Time Registration"

Base Application · Microsoft.Integration.Graph

Open in Claude5513.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 5510 "Employee Time Reg Buffer" (calls, 3 links)Employee Time Reg BufferCodeunit 5465 "Graph Mgt - General Tools" (calls)Graph Mgt - General Tools

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

Procedures

  • InitUserSetup()
  • ModifyResourceToUseTimeSheet(var Resource: Record Resource)
  • CreateResourceToUseTimeSheet(var Resource: Record Resource)
  • GetTimeSheetHeader(ResouceNo: Code[20]; StartingDate: Date): Code[20]
  • GetTimeSheetLineWithEmptyDate(var TimeSheetLine: Record "Time Sheet Line"; TimeSheetHeaderNo: Code[20]; TimeSheetDetailDate: Date)
  • AddTimeSheetDetail(var TimeSheetDetail: Record "Time Sheet Detail"; TimeSheetLine: Record "Time Sheet Line"; Date: Date; Quantity: Decimal)
  • AddTimeSheetDetailWithDimensionSetAndJob(var TimeSheetDetail: Record "Time Sheet Detail"; TimeSheetLine: Record "Time Sheet Line"; Date: Date; Quantity: Decimal; DimensionSetID: Integer; JobID: Guid)

Plus 3 local procedures.

Triggers

OnRun

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.

Called by

  • Table 5510 “Employee Time Reg Buffer” (3 calls: PropagateInsert → AddTimeSheetDetailWithDimensionSetAndJob, PropagateInsert → GetTimeSheetHeader, PropagateInsert → GetTimeSheetLineWithEmptyDate)

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: "Graph Mgt - Time Registration"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources