Page 760 "Trailing Sales Orders Chart"
Base Application · Microsoft.Sales.Analysis
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Analysis · captioned “Trailing Sales Orders” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Trailing Sales Orders |
| SourceTable | Business Chart Buffer |
| 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 |
|---|---|---|---|
| Show | All Orders | View all not fully posted sales orders, including sales orders with document dates in the future because of long delivery times, delays, or other reasons. | |
| Orders Until Today | View not fully posted sales orders with document dates up until today’s date. | ||
| Delayed Orders | View not fully posted sales orders with shipment dates that are before today’s date. | ||
| Period Length | Day | Each stack covers one day. | |
| Week | Each stack except for the last stack covers one week. The last stack contains data from the start of the week until the date that is defined by the Show option. | ||
| Month | Each stack except for the last stack covers one month. The last stack contains data from the start of the month until the date that is defined by the Show option. | ||
| Quarter | Each stack except for the last stack covers one quarter. The last stack contains data from the start of the quarter until the date that is defined by the Show option. | ||
| Year | Each stack except for the last stack covers one year. The last stack contains data from the start of the year until the date that is defined by the Show option. | ||
| Value to Calculate | Amount | The Y-axis shows the totaled LCY amount of the orders. | |
| No. of Orders | The Y-axis shows the number of orders. | ||
| Chart Type | Stacked Area | View the data in area layout. | |
| Stacked Area (%) | view the percentage distribution of the four order statuses in area layout. | ||
| Stacked Column | view the data in column layout. | ||
| Stacked Column (%) | view the percentage distribution of the four order statuses in column layout. | ||
| Processing | Setup | Specify if the chart will be based on a work date other than today’s date. This is mainly relevant in demonstration databases with fictitious sales orders. |
Procedures
SetActionsEnabled(): Updates the enabled state of chart action buttons based on current settings.
Plus 3 local procedures.
Triggers
OnFindRecord, OnOpenPage
Relations
- source table Table 485 “Business Chart Buffer”
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 760 “Trailing Sales Orders Mgt.” (1 call:
UpdateChart → UpdateData) - Page 761 “Trailing Sales Orders Setup” (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 Chart"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.