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

Table 6130 "E-Doc. File Content API Buffer"

EDocument · Microsoft.eServices.EDocument.API

Across versions

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

Neighbourhood 3 connected objects and pages

Table 6103 "E-Document Service" (relates to)E-Document ServiceTable 6121 "E-Document" (relates to)E-DocumentPage 6119 "E-Doc. File Content API" (pages and codeunits on it)E-Doc. File Content API

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.API · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption E-Doc. File Content API Buffer
Access Internal
TableType Temporary
DataClassification CustomerContent

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-Doc Entry No. Integer Specifies the unique identifier of the E-Document TableRelation Table 6121 “E-Document” (E-Document); DataClassification SystemMetadata
2 E-Document Service Code Code[20] Specifies the service code of the E-Document TableRelation Table 6103 “E-Document Service” (E-Document Service); DataClassification SystemMetadata
3 E-Document Service Status Enum “E-Document Service Status” Specifies the status of the E-Document Service enum Enum 6106 “E-Document Service Status”; DataClassification SystemMetadata
4 Content Blob Specifies the file contents of the E-Document

Keys

  • Key1: E-Doc Entry No., E-Document Service Code, E-Document Service Status (clustered)

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: "E-Doc. File Content API Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources