Page 394 "Entry/Exit Points"
Base Application · Microsoft.Inventory.Intrastat
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Intrastat · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Entry/Exit Points |
| SourceTable | Entry/Exit Point |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | BasicEU, BasicNO |
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 | Code | Code | Specifies the code for the shipping location (Entry/Exit Point). from the table field |
| Description | Description | Specifies a description of the shipping location (Entry/Exit Point). from the table field |
Relations
- source table Table 282 “Entry/Exit Point”
Pages and codeunits on this table
- Table 282 “Entry/Exit Point” (drill-down page)
- Table 282 “Entry/Exit Point” (lookup page)
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: "Entry/Exit Points"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.