BC Observatoryunofficial, made by waldo
tableextensionSales & Receivablesofficial - Microsoftderived - from the source, no model text

Table extension 6172 "E-Doc. Sales Header"

EDocument · Microsoft.Sales.Document

Open in Claude6172.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Table 36 "Sales Header" (relates to)Sales Header

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

Extends Sales Header.

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
6102 E-Document Link Guid — not editable; DataClassification SystemMetadata

Keys

  • EDocKey1: E-Document Link

Procedures

  • IsLinkedToEDoc(EDocumentToExclude: Record "E-Document"): Boolean (internal)

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: "tableextension", object_name: "E-Doc. Sales Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources