pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 6101 "E-Doc. Purch. Line Fields"

EDocument · Microsoft.eServices.EDocument.Processing.Import

Across versions

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

Neighbourhood 1 connected objects and pages

Table 6112 "ED Purchase Line Field Setup" (relates to)ED Purchase Line Field Setup

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.

EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Extensible false
SourceTable ED Purchase Line Field Setup
PageType ListPart

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
LineFields Field No. Field No. Specifies the number of the field in the table.
Field Name Name Specifies the name of the field in the table.
Consider additional field AddAdditionalField Specifies whether to consider this additional field for new inbound e-documents.
Application OwnerApp Specifies the application that owns the field.

Procedures

  • SetEDocumentService(EDocumentService: Record "E-Document Service") (internal)

Triggers

OnOpenPage, OnAfterGetRecord

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: "page", object_name: "E-Doc. Purch. Line Fields"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources