Page 971 "Activity Details FactBox"
Base Application · Microsoft.Projects.TimeSheet
Across versions
- BC23-24present
- BC251 events added
- BC26-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Projects.TimeSheet · captioned “Activity Details” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Activity Details |
| SourceTable | Time Sheet Line |
| PageType | CardPart |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Content | Line Comment | Comment | Specifies that a comment about this document has been entered. from the table field |
| Line Total | Total Quantity | Specifies the total number of hours that have been entered on a time sheet. from the table field | |
| ActivitiID | ActivitiID |
— | |
| ActivitySubID | ActivitySubID |
— |
Events published
OnBeforeLookupSubActivity(TimeSheetLine: Record "Time Sheet Line"; var IsHandled: Boolean)(integration)OnLookupActivity(var TimeSheetLine: Record "Time Sheet Line")+ BC25 (integration)- subscribers: Codeunit 6451 “Serv. Time Sheet Mgt.” OnLookupActivity
Procedures
SetEmptyLine()
Plus 2 local procedures.
Triggers
OnAfterGetRecord
Relations
- source table Table 951 “Time Sheet Line”
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” (1 call:
OnAfterGetRecord → GetActivityInfo)
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: "page", object_name: "Activity Details FactBox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.