BC Observatoryunofficial, made by waldo
pageextensionInventoryofficial - Microsoftderived - from the source, no model text

Page extension 1856 "PurchaseOrderForecastExtension"

SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast

Open in Claude1856.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Page 50 "Purchase Order" (relates to)Purchase Order

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.

SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast · BC29-30 · source at ea08af5e · facts from BC29

Extends Purchase Order.

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
addafter(WorkflowStatus) ItemForecast part Page 1850 “Sales Forecast” —

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "pageextension", object_name: "PurchaseOrderForecastExtension"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources