Codeunit 109 "Lookup State Manager"
Base Application · Microsoft.Utilities
Across versions
- BC23-30present
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Utilities · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SingleInstance | true |
Procedures
GetSavedRecord(): VariantClearSavedRecord()IsRecordSaved(): BooleanSaveRecord(var RecordVariant: Variant)
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.
- Table 37 “Sales Line” (4 calls:
RestoreLookupSelectionWithResult → ClearSavedRecord,RestoreLookupSelectionWithResult → GetSavedRecord,RestoreLookupSelectionWithResult → IsRecordSaved, …) - Table 39 “Purchase Line” (4 calls:
RestoreLookupSelection → ClearSavedRecord,RestoreLookupSelection → GetSavedRecord,RestoreLookupSelection → IsRecordSaved, …) - Page 50 “Purchase Order” (2 calls:
OnNewRecord → ClearSavedRecord,OnNewRecord → IsRecordSaved) - Table 38 “Purchase Header” (2 calls:
LookupBuyFromVendorName → SaveRecord,LookupPayToVendorName → SaveRecord) - Table 1001 “Job Task” (1 call:
LookupSellToCustomerName → SaveRecord) - Table 167 “Job” (1 call:
LookupSellToCustomerName → SaveRecord) - Table 36 “Sales Header” (1 call:
LookupSellToCustomerName → SaveRecord)
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: "Lookup State Manager"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.