BC Observatoryunofficial, made by waldo
pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 6104 "E-Doc. Line Additional Fields"

EDocument · Microsoft.EServices.EDocument.Processing.Import

Open in Claude6104.mdSource on GitHub

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 · captioned “Additional fields” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Additional fields
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
Fields Field Name this.FieldName Specifies the field name.
Field Value FieldValue Specifies the value for this field.

Actions

Group Action ToolTip Runs
Processing Revert Changes Revert changes back to it’s original values.

Procedures

  • SetEDocumentLine(EDocumentPurchaseLine: Record "E-Document Purchase Line"; PurchaseInvoiceLine: Record "Purch. Inv. Line") (internal)

Triggers

OnOpenPage, OnAfterGetRecord, OnAfterGetCurrRecord

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. Line Additional Fields"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources