Codeunit 104 "Update Name In Ledger Entries"

Base Application · Microsoft.Upgrade · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnUpdateCustNamesInLedgerEntriesOnBeforeModifyCustLedgEntry(var CustLedgerEntry: Record "Cust. Ledger Entry"; Customer: Record Customer) (integration)
• OnUpdateVendNamesInLedgerEntriesOnBeforeModifyVendLedgEntry(var VendorLedgerEntry: Record "Vendor Ledger Entry"; Vendor: Record Vendor) (integration)
• OnUpdateDescriptionInWarehouseLedgerEntriesOnBeforeModifyWarehouseEntry(var WarehouseEntry: Record "Warehouse Entry"; Item: Record Item; ItemVariant: Record "Item Variant") + BC24 (integration)

Procedures

• ScheduleUpdate(Notification: Notification)
• NotifyAboutBlankNamesInLedgerEntries(SetupRecordID: RecordID)
• UpdateCustNamesInLedgerEntries()
• UpdateItemDescrInLedgerEntries()
• UpdateVendNamesInLedgerEntries()

Plus 13 local procedures.

Triggers

OnRun

Relations

• runs on Table 472 “Job Queue Entry”

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 1511 “Notification Lifecycle Mgt.” (1 call: NotifyAboutBlankNamesInLedgerEntries → SendNotification)

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: "Update Name In Ledger Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.