Table 22216 "G/L Entry Review Entry"
ReviewGLEntries · Microsoft.Finance.GeneralLedger.Review
Across versionsobsolete pending since 27.0
- BC23-28not present
- BC29-30present
ReviewGLEntries · Microsoft.Finance.GeneralLedger.Review · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| ObsoleteState | Pending |
| ObsoleteTag | 27.0 |
| ObsoleteReason | Use “G/L Entry Review Log” instead. |
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 | G/L Entry No. | Integer | — | DataClassification SystemMetadata |
| 2 | Reviewed Identifier | Integer | — | DataClassification SystemMetadata |
| 3 | Reviewed By | Code[50] | — | DataClassification EndUserIdentifiableInformation |
Keys
- GLEntryNo: G/L Entry No. (clustered)
Triggers
OnInsert, OnDelete
Deprecations
- object: Pending 27.0 (#if not CLEANSCHEMA27), “Use “G/L Entry Review Log” instead.”
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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 Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.