Codeunit 270 "ResJnlManagement"
Base Application · Microsoft.Projects.Resources.Journal
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Projects.Resources.Journal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Permissions | TableData “Res. Journal Template” = rimd, TableData “Res. Journal Batch” = rimd |
Events published
OnBeforeOpenJnl(var CurrentJnlBatchName: Code[10]; var ResJournalLine: Record "Res. Journal Line")(integration)
Procedures
TemplateSelection(PageID: Integer; RecurringJnl: Boolean; var ResJnlLine: Record "Res. Journal Line"; var JnlSelected: Boolean)TemplateSelectionFromBatch(var ResJnlBatch: Record "Res. Journal Batch")OpenJnl(var CurrentJnlBatchName: Code[10]; var ResJnlLine: Record "Res. Journal Line")OpenJnlBatch(var ResJnlBatch: Record "Res. Journal Batch")CheckName(CurrentJnlBatchName: Code[10]; var ResJnlLine: Record "Res. Journal Line")SetName(CurrentJnlBatchName: Code[10]; var ResJnlLine: Record "Res. Journal Line")LookupName(var CurrentJnlBatchName: Code[10]; var ResJnlLine: Record "Res. Journal Line")GetRes(ResNo: Code[20]; var ResName: Text[100])
Plus 1 local procedures.
Triggers
OnRun
Called by
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.
- Page 207 “Resource Journal” (4 calls:
CurrentJnlBatchNameOnAfterVali → SetName,OnAfterGetCurrRecord → GetRes,OnOpenPage → OpenJnl, …) - Page 290 “Recurring Resource Jnl.” (4 calls:
CurrentJnlBatchNameOnAfterVali → SetName,OnAfterGetCurrRecord → GetRes,OnOpenPage → OpenJnl, …) - Page 272 “Resource Jnl. Batches” (1 call:
OnOpenPage → OpenJnlBatch)
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: "ResJnlManagement"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.