Page 1924 "Profiling Duration By Method"
System Application · System.Tooling
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
System Application · System.Tooling · captioned “Application calls” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Application calls |
| SourceTable | Profiling Node |
| PageType | ListPart |
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 |
|---|---|---|---|
| Duration per line of code | Method Name | Method Name | Specifies the name of the method in which the time was spent. |
| Time Spent | Self Time | Specifies the total time spent inside the method during the performance profiler recording. |
Procedures
Initialize(AppObjectType: Text; AppObjectId: Integer)(internal)
Relations
- source table Table 1921 “Profiling Node”
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 1923 “Profiling Data Processor” (1 call:
Initialize → GetSelfTimeAggregate)
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: "Profiling Duration By Method"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.