Codeunit 15 "Gen. Jnl.-Show Card"
Base Application · Microsoft.Finance.GeneralLedger.Journal
Across versions
- BC23-30present
Neighbourhood 9 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Journal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Gen. Journal Line |
Events published
OnAfterRun(GenJournalLine: Record "Gen. Journal Line")(integration): Integration event raised after displaying account card page from journal line. Enables custom processing after account card navigation is completed.
Triggers
OnRun
Relations
- runs on Table 81 “Gen. Journal Line”
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.
- Page 17 “G/L Account Card” (1 call:
OnRun → (object)) - Page 21 “Customer Card” (1 call:
OnRun → (object)) - Page 26 “Vendor Card” (1 call:
OnRun → (object)) - Page 370 “Bank Account Card” (1 call:
OnRun → (object)) - Page 5200 “Employee Card” (1 call:
OnRun → (object)) - Page 5600 “Fixed Asset Card” (1 call:
OnRun → (object)) - Page 609 “IC Partner Card” (1 call:
OnRun → (object))
Called by
- Page 1693 “Bank Deposit Subform” (1 call:
ShowAccountCard → (object))
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: "Gen. Jnl.-Show Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.