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

Table 22217 "G/L Entry Review Setup"

ReviewGLEntries · Microsoft.Finance.GeneralLedger.Review

Open in Claude22217.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Page 22206 "G/L Entry Review Setup" (pages and codeunits on it)G/L Entry Review Setup

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.

ReviewGLEntries · Microsoft.Finance.GeneralLedger.Review · BC29-30 · source at ea08af5e · facts from BC29

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 Primary Key Code[10] — DataClassification SystemMetadata
2 GLEntryReviewer Enum “G/L Entry Reviewer” Specifies which review implementation the review system uses via Page 22206 “G/L Entry Review Setup” enum Enum 22202 “G/L Entry Reviewer”; DataClassification SystemMetadata

Keys

  • Key1: Primary Key (clustered)

Pages and codeunits on this table

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: "G/L Entry Review Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources