codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 1926 "Profiling Chart Helper"

System Application · System.Tooling

Across versions

  1. BC23present
  2. BC241 procedures added, 1 procedures removed
  3. BC25-30unchanged

Neighbourhood 4 connected objects and pages

Codeunit 479 "Business Chart" (calls, 6 links)Business ChartCodeunit 1923 "Profiling Data Processor" (calls, 3 links)Profiling Data ProcessorPage 1922 "Profiling Self Time Chart" (calls)Profiling Self Time ChartPage 1925 "Profiling Full Time Chart" (calls)Profiling Full Time Chart

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

Properties

Property Value
Access Internal

Procedures

  • GetChartData(ProfilingAggregationType: Enum "Profiling Aggregation Type"; AggregateBySelfTime: Boolean; ChartLabels: List of [Text]; ChartValues: List of [Integer]): Gets the dictionary with aggregation type identifiers as keys, and aggregated self time / full time as values.
  • UpdateData(BusinessChartControlAddIn: ControlAddIn BusinessChart; ProfilingAggregationType: Enum "Profiling Aggregation Type"; BusinessChartType: Enum "Business Chart Type"; AggregateBySelfTime: Boolean) + BC24 − BC24: Updates the contents of the business chart control add-in for performance profiler charts.

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

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

Evidence 1 sources