Table 2583 "Dim Correction Entry Log"
Base Application · Microsoft.Finance.Dimension.Correction
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Finance.Dimension.Correction · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| 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 | Dimension Correction Entry No. | Integer | — | TableRelation Table 2582 “Dimension Correction” (“Dimension Correction”.“Entry No.”) |
| 2 | Start Entry No. | Integer | — | TableRelation Table 2582 “Dimension Correction” (“Dimension Correction”.“Entry No.”) |
| 3 | End Entry No. | Integer | — | TableRelation Table 2582 “Dimension Correction” (“Dimension Correction”.“Entry No.”) |
Keys
- Key1: Dimension Correction Entry No., Start Entry No., End Entry No.
Relations
- Dimension Correction Entry No.: TableRelation Table 2582 “Dimension Correction”
- End Entry No.: TableRelation Table 2582 “Dimension Correction”
- Start Entry No.: TableRelation Table 2582 “Dimension Correction”
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: "Dim Correction Entry Log"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.