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

Page 130405 "CAL Test Results"

Base Application · System.TestTools.TestRunner

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 130405 "CAL Test Result" (relates to)CAL Test ResultTable 130401 "CAL Test Line" (calls)CAL Test Line

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

Properties

Property Value
Caption CAL Test Results
SourceTable CAL Test Result
PageType List

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
Repeater No. No. Specifies the number of the involved entry or record, according to the specified number series.
Test Run No. Test Run No. —
Codeunit ID Codeunit ID —
Codeunit Name Codeunit Name —
Function Name Function Name —
Platform Platform —
Result Result —
Restore Restore —
Start Time Start Time —
Execution Time Execution Time —
Error Message Error Message —
User ID User ID Specifies the ID of the user who posted the entry, to be used, for example, in the change log.
File File —

Actions

Group Action ToolTip Runs
Creation Call Stack —
Export —

Procedures

1 local procedures, no public ones.

Triggers

OnAfterGetRecord

Relations

Called by

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.

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: "CAL Test Results"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources