Page 1851 "Sales Forecast No Chart"
SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 4 connected objects and pages
SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast · captioned “Forecast” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Forecast |
| SourceTable | Item |
| 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 |
|---|---|---|---|
| Disclaimer | DisclaimerText | DisclaimerValueMsg |
AI generated suggestions may not always be accurate. Please validate results for correctness before using content provided. |
| Content | Status | StatusTextValue |
Specifies the status of the forecast based on the current setup data. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Forecast Settings | View or edit the setup for the forecast. |
Events published
OnAfterHasMinimumSIHistData(ItemNo: Code[20]; var HasMinimumHistoryLoc: boolean; var NumberOfPeriodsWithHistoryLoc: Integer; PeriodType: Integer; ForecastStartDate: Date; var StatusType: Option " ","No columns due to high variance","Limited columns due to high variance","Forecast expired","Forecast period type changed","Not enough historical data","Zero Forecast","No Forecast available")(integration)
Procedures
UpdateStatus()
Plus 2 local procedures.
Triggers
OnAfterGetRecord, OnInit
Relations
- source table Table 27 “Item”
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 2000 “Time Series Management” (3 calls:
UpdateStatus → HasMinimumHistoricalData,UpdateStatus → SetMaximumHistoricalPeriods,UpdateStatus → SetMinimumHistoricalPeriods) - Codeunit 1850 “Sales Forecast Handler” (1 call:
UpdateStatus → SetItemLedgerEntryFilters)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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 Forecast No Chart"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.