codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 15 "Gen. Jnl.-Show Card"

Base Application · Microsoft.Finance.GeneralLedger.Journal

Across versions

  1. BC23-30present

Neighbourhood 9 connected objects and pages

Table 81 "Gen. Journal Line" (relates to)Gen. Journal LinePage 1693 "Bank Deposit Subform" (calls)Bank Deposit SubformPage 17 "G/L Account Card" (calls)G/L Account CardPage 21 "Customer Card" (calls)Customer CardPage 26 "Vendor Card" (calls)Page 370 "Bank Account Card" (calls)Bank Account CardPage 5200 "Employee Card" (calls)Employee CardPage 5600 "Fixed Asset Card" (calls)Fixed Asset CardPage 609 "IC Partner Card" (calls)IC Partner Card

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.

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

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.

Called by

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.

Evidence 1 sources