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

Table 6110 "E-Document Line - Field"

EDocument · Microsoft.eServices.EDocument.Processing.Import

Across versions

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

Neighbourhood 1 connected objects and pages

Table 6121 "E-Document" (relates to, 2 links)E-Document

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 “E-Document Line Field” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption E-Document Line Field
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 E-Document Entry No. Integer Specifies the entry number of the e-document. TableRelation Table 6121 “E-Document” (“E-Document”.“Entry No”); DataClassification SystemMetadata
2 Line No. Integer Specifies the line number. DataClassification SystemMetadata
3 Field No. Integer Specifies the field number. DataClassification SystemMetadata
4 Text Value Text[2048] Specifies the custom text value. DataClassification CustomerContent
5 Decimal Value Decimal Specifies the custom decimal value. DataClassification CustomerContent
6 Date Value Date Specifies the custom date value. DataClassification CustomerContent
7 Boolean Value Boolean Specifies the custom boolean value. DataClassification CustomerContent
8 Code Value Code[2048] Specifies the custom code value. DataClassification CustomerContent
9 Integer Value Integer Specifies the custom integer value. DataClassification CustomerContent
10 E-Document Service Code[20] Specifies the E-Document Service that this field setup belongs to. FlowField: lookup(“E-Document”.Service where(“Entry No” = field(“E-Document Entry No.”)))

Keys

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

Procedures

  • Get(EDocumentPurchaseLine: Record "E-Document Purchase Line"; PurchaseLineFieldSetup: Record "ED Purchase Line Field Setup"): Option Customized,Historic,Default: Sets the current record to have the values corresponding to the line for a given purchase invoice line field if there is no existing customization of the historic values (a physical record of this table) it loads the appropriate values from history. The history is loaded according to the EDocumentLi…
  • GetValue(): Variant
  • InsertOrModify()
  • GetValueAsText(): Text
  • HasCustomizedRecords(EDocumentPurchaseLine: Record "E-Document Purchase Line"): Boolean
  • DeleteCustomizedRecords(EDocumentPurchaseLine: Record "E-Document Purchase Line")

Plus 1 local procedures.

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

Evidence 1 sources