Codeunit 5061 "SegHistoryManagement"
Base Application · Microsoft.CRM.Segment
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.CRM.Segment · BC23-30 · source at ea08af5e · facts from BC29
Events published
OnAfterInitLine(SegmentNo: Code[20]; var SegmentHistory: Record "Segment History")(integration)
Procedures
InsertLine(SegmentNo: Code[20]; ContactNo: Code[20]; LineNo: Integer)DeleteLine(SegmentNo: Code[20]; ContactNo: Code[20]; LineNo: Integer)GoBack(SegmentNo: Code[20])
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 5092 “Segment Subform” (4 calls:
OnDeleteRecord → DeleteLine,OnInsertRecord → InsertLine,OnModifyRecord → DeleteLine, …) - Report 5186 “Remove Contacts” (1 call:
UpdateSegLines → DeleteLine) - Report 5198 “Add Contacts” (1 call:
UpdateSegLines → InsertLine) - Table 5076 “Segment Header” (1 call:
ReuseLogged → InsertLine)
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: "SegHistoryManagement"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.