Page 781 "Sales Pipeline Chart"
Base Application · Microsoft.Sales.Analysis
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Sales.Analysis · captioned “Sales Pipeline” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Sales Pipeline |
| 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 | Status Text | StatusText |
Specifies the status of the chart. |
| BusinessChart | add-in BusinessChart | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Previous Sales Cycle | View the previous chart. | |
| Next Sales Cycle | View the next chart. |
Procedures
UpdateChart(SalesCycle: Record "Sales Cycle")(protected)
Plus 1 local procedures.
Triggers
OnOpenPage
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 781 “Sales Pipeline Chart Mgt.” (2 calls:
OnOpenPage → SetDefaultSalesCycle,UpdateChart → UpdateData)
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: "Sales Pipeline Chart"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.