Table 8400 "Record Set Definition"
Base Application · System.IO
Across versions
- BC23present
- BC241 fields changed
- BC25-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Record Set Definition |
| 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 | Table No. | Integer | — | |
| 2 | Set ID | Integer | — | AutoIncrement |
| 3 | Node ID | Integer | — | |
| 10 | Value Δ BC24 | RecordID | — | FlowField: lookup (“Record Set Tree”.Value where(“Table No.” = field(“Table No.”), “Node ID” = field(“Node ID”))) |
Keys
- Key1: Table No., Set ID, Node ID (clustered)
Relations
- Value: CalcFormula Table 8401 “Record Set Tree”
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: "Record Set Definition"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.