Page 191 "Incoming Documents Setup"
Base Application · Microsoft.EServices.EDocument
Across versions
- BC23-25present
- BC26declaration changed
- BC27-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.EServices.EDocument · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Incoming Documents Setup |
| SourceTable | Incoming Documents Setup |
| PageType | Card |
| UsageCategory | Administration |
| ApplicationArea | Suite |
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 |
|---|---|---|---|
| Content | General Journal Template Name | General Journal Template Name | Specifies the type of the general journal that new journal lines are created in when you choose the Journal Line button in the Incoming Documents window. from the table field |
| General Journal Batch Name | General Journal Batch Name | Specifies the subtype of the general journal that new journal lines are created in when you choose the Journal Line button in the Incoming Documents window. from the table field | |
| Require Approval To Create | Require Approval To Create | Specifies whether the incoming document line must be approved before a document or journal line can be created from the Incoming Documents window. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Navigation | Approvers | View or add incoming document approvers. | Page 192 “Incoming Document Approvers” |
Triggers
OnOpenPage
Relations
- source table Table 131 “Incoming Documents Setup”
Pages and codeunits on this table
- Table 131 “Incoming Documents Setup” (drill-down page)
- Table 131 “Incoming Documents Setup” (lookup page)
- Table 1660 “Payroll Setup” (drill-down page)
- Table 1660 “Payroll Setup” (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: "Incoming Documents Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.