Page 761 "Trailing Sales Orders Setup"

Base Application · Microsoft.Sales.Analysis · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Trailing Sales Orders Setup
SourceTable	Trailing Sales Orders Setup
PageType	StandardDialog

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
General	Use Work Date as Base	Use Work Date as Base	Specifies if you want data in the Trailing Sales Orders chart to be based on a work date other than today’s date. This is generally relevant when you view the chart data in a demonstration database that has fictitious sales orders. from the table field

Triggers

OnOpenPage

Relations

source table Table 760 “Trailing Sales Orders Setup”

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.

Page 760 “Trailing Sales Orders Chart” (1 call: RunSetup → (object))

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: "Trailing Sales Orders Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.