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

Page 6102 "E-Doc Line Values."

EDocument · Microsoft.EServices.EDocument.Processing.Import

Open in Claude6102.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Table 6101 "E-Document Purchase Line" (relates to)E-Document Purchase Line

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 E-Document Purchase Line
PageType Card

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 Source RetrievedFromTxt Specifies the source of the values in this line.
EDocLineHistFields part Page 6104 “E-Doc. Line Additional Fields” —

Actions

Group Action ToolTip Runs
Navigation Configure additional fields Configure the additional fields to consider when importing an E-Document.

Triggers

OnOpenPage

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

Evidence 1 sources