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

Table 6112 "ED Purchase Line Field Setup"

EDocument · Microsoft.eServices.EDocument.Processing.Import

Open in Claude6112.mdSource on GitHub

Across versions

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

Neighbourhood 3 connected objects and pages

Table 6103 "E-Document Service" (relates to)E-Document ServicePage 6101 "E-Doc. Purch. Line Fields" (pages and codeunits on it)E-Doc. Purch. Line FieldsPage 6104 "E-Doc. Line Additional Fields" (pages and codeunits on it)E-Doc. Line Additional Fields

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
Access Internal

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Field No. Integer Specifies the number of the field in the table. via Page 6101 “E-Doc. Purch. Line Fields” not editable; DataClassification SystemMetadata
2 E-Document Service Code[20] Specifies the E-Document Service that this field setup belongs to. TableRelation Table 6103 “E-Document Service” (E-Document Service); DataClassification SystemMetadata

Keys

  • PK: Field No., E-Document Service (clustered)

Procedures

  • AllPurchaseLineFields(EDocumentService: Record "E-Document Service"; var EDocPurchLineFieldSetup: Record "ED Purchase Line Field Setup" temporary): Populates the contents of the temporary table “ED Purchase Line Field Setup” with the fields from the “Purch. Inv. Line” table that can be configured for e-document history. The fields are loaded with the default configuration if the user has not set up any specific configuration.
  • ApplySetup(ConsiderField: Boolean; EDocPurchLineFieldSetup: Record "ED Purchase Line Field Setup"): Persist the changes in the parameter to the configuration
  • DeleteOmittedFieldsIfConfigured() (internal)
  • IsOmitted(): Boolean (internal)

Plus 1 local procedures.

Triggers

OnDelete

Relations

Pages and codeunits on this table

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: "table", object_name: "ED Purchase Line Field Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources