Page 5430 "Planning Error Log"
Base Application · Microsoft.Inventory.Planning
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Inventory.Planning · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Planning Error Log |
| SourceTable | Planning Error Log |
| PageType | List |
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 |
|---|---|---|---|
| Control1 | Item No. | Item No. | Specifies the item number associated with this entry. from the table field |
| Error Description | Error Description | Specifies the description to the error in this entry. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Show | View the log details. |
Relations
- source table Table 5430 “Planning Error Log”
Pages and codeunits on this table
- Table 5430 “Planning Error Log” (drill-down page)
- Table 5430 “Planning Error Log” (lookup page)
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). 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: "Planning Error Log"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.