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

Table 6508 "Value Entry Relation"

Base Application · Microsoft.Inventory.Ledger

Open in Claude6508.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Table 5802 "Value Entry" (relates to)Value 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.Inventory.Ledger · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Value Entry Relation
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 Value Entry No. Integer — TableRelation Table 5802 “Value Entry” (Value Entry)
11 Source RowId Text[250] —

Keys

  • Key1: Value Entry No. (clustered)
  • Key2: Source RowId

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

Evidence 1 sources