Page extension 6132 "E-Doc. Purchase Order"
EDocument · Microsoft.Purchases.Document
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.Purchases.Document · 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 |
|---|---|---|---|
| addlast(General) | Linked with E-Document | (not IsNullGuid(Rec."E-Document Link")) |
— |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| E-Document | Map E-Document Lines | Map received E-Document to the Purchase Order | |
| Preview E-Document Mapping | Preview E-Document Mapping | ||
| addlast(Prompting) | Map E-Document Lines obsolete Pending 29.0; #if not CLEAN29 | Map received E-Document to the Purchase Order |
Triggers
OnAfterGetCurrRecord
Relations
- extends Page 50 “Purchase Order”
Recent changes
- 2026-09-24 #11483 [E-Documents Core] - Linkage & Traceability (main, BC30, feature)
- 2026-08-06 #9954 Restoring undefined action. (Purchase Orders page can’t be open in latest
main) (main, BC30, fix) - 2026-07-22 #9572 Obsolete E-Document Purchase Order Matching Copilot (main, BC30, obsoletion)
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: "E-Doc. Purchase Order"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.