Codeunit 952 "Time Sheet Chart Mgt."

Base Application · Microsoft.Projects.TimeSheet · BC23-30 · source at ea08af5e · facts from BC29

Events published

• OnAddColumnsOnAfterSetFilters(var Resource: Record Resource) (integration)

Procedures

• OnOpenPage(var TimeSheetChartSetup: Record "Time Sheet Chart Setup")
• UpdateData(var BusChartBuf: Record "Business Chart Buffer")
• DrillDown(var BusChartBuf: Record "Business Chart Buffer")
• CalcAmount(TimeSheetChartSetup: Record "Time Sheet Chart Setup"; ResourceNo: Code[249]; MType: Integer): Decimal
• GetMeasureCaption(Type: Option): Text

Plus 2 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.

• Codeunit 950 “Time Sheet Management” (2 calls: DrillDown → SetTimeSheetNo, OnOpenPage → FindNearestTimeSheetStartDate)
• Page 224 “Res. Capacity Entries” (1 call: DrillDown → (object))
• Page 952 “Manager Time Sheet” (1 call: DrillDown → (object))
• Page 958 “Time Sheet Posting Entries” (1 call: DrillDown → (object))

Called by

• Page 972 “Time Sheet Chart” (1 call: UpdateChart → UpdateData)

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