BC Observatoryunofficial, made by waldo
tableextensionProjectsofficial - Microsoftderived - from the source, no model text

Table extension 6459 "Serv. Job Ledger Entry"

Base Application · Microsoft.Projects.Project.Ledger

Open in Claude6459.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Table 169 "Job Ledger Entry" (relates to)Job Ledger Entry

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.

Base Application · Microsoft.Projects.Project.Ledger · BC25-30 · source at ea08af5e · facts from BC29

Extends Job Ledger Entry.

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
5900 Service Order No. Code[20] — DataClassification CustomerContent
5901 Posted Service Shipment No. Code[20] — DataClassification CustomerContent

Keys

  • Key6: Service Order No.

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. Job Ledger Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources