Codeunit 22200 "Review G/L Entry"
ReviewGLEntries · Microsoft.Finance.GeneralLedger.Review
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
ReviewGLEntries · Microsoft.Finance.GeneralLedger.Review · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Permissions | TableData “G/L Entry” = rm, TableData “G/L Entry Review Setup” = ri, #if not CLEAN27 #pragma warning disable AL0432 TableData “G/L Entry Review Entry” = rid, #pragma warning restore AL0432 #endif TableData “G/L Entry Review Log” = rid |
Events published
OnAfterReviewEntries(var GLEntry: Record "G/L Entry"; var GLEntryReviewEntry: Record "G/L Entry Review Entry")(integration, obsolete 27.0)OnAfterReviewEntriesLog(var GLEntry: Record "G/L Entry"; var GLEntryReviewLog: Record "G/L Entry Review Log")(integration)
Event subscriptions
- OnAfterInitSetupTables subscribes to Codeunit “Company-Initialize” OnAfterInitSetupTables
- OnSkipGLEntryByReviewStatus subscribes to Table “G/L Entry” OnSkipGLEntryByReviewStatus
Procedures
ReviewEntries(var GLEntry: Record "G/L Entry")UnreviewEntries(var GLEntry: Record "G/L Entry")ValidateEntries(var GLEntry: Record "G/L Entry")
Plus 3 local procedures.
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 8703 “Feature Telemetry” (2 calls:
ReviewEntries → LogUptake,ReviewEntries → LogUsage)
Implements
Deprecations
- procedure OnAfterReviewEntries: Pending 27.0 (#if not CLEAN27), “Use the event OnAfterReviewEntriesLog 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). The call sections above are our own, per object, from the BC29 call graph. 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: "codeunit", object_name: "Review G/L Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.