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

Table extension 5020 "Serv. Decl. Sales Line"

ServiceDeclaration · Microsoft.Sales.Document

Open in Claude5020.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Table 37 "Sales Line" (relates to)Sales LineTable 5011 "Service Transaction Type" (relates to)Service Transaction Type

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.

ServiceDeclaration · Microsoft.Sales.Document · BC29-30 · source at ea08af5e · facts from BC29

Extends Sales Line.

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
5010 Service Transaction Type Code Code[20] Specifies the code for a service transaction type. via Page extension 5018 “SD Sales Cr. Memo Subform” TableRelation Table 5011 “Service Transaction Type” (Service Transaction Type)
5011 Applicable For Serv. Decl. Boolean Specifies whether an item or resource is applicable for a service declaration. via Page extension 5018 “SD Sales Cr. Memo Subform”

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: "Serv. Decl. Sales Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources