Codeunit 3111 "Activity Log Builder"
System Application · System.Log
Across versions
- BC23-25not present
- BC26added
- BC271 procedures added
- BC281 procedures added
- BC29-30unchanged
Neighbourhood 1 connected objects and pages
System Application · System.Log · BC26-30 · source at ea08af5e · facts from BC29
Procedures
Init(TableNo: Integer; FieldNo: Integer; RecSystemId: Guid): Codeunit "Activity Log Builder": Initializes the activity log builder for a specific table and field.SetExplanation(Explanation: Text): Codeunit "Activity Log Builder": Sets the explanation for the activity log entry.SetType(Type: Enum "Activity Log Type"): Codeunit "Activity Log Builder": Sets the type of the activity log entry. Allowed values are “AI” for AI-related activities and “AL” for general activitiesSetConfidence(Confidence: Text): Codeunit "Activity Log Builder"+ BC27: Sets the confidence level for the activity log value.SetReferenceSource(PageId: Integer; var Rec: RecordRef): Codeunit "Activity Log Builder": Sets the reference source for the activity log entry. The reference source can be a page ID and a record reference, which will be converted to a URL.SetReferenceSource(ReferenceSource: Text): Codeunit "Activity Log Builder": Sets the reference source for the activity log entry. This can be a URL or any other text that identifies the source of the reference.SetReferenceTitle(ReferenceTitle: Text): Codeunit "Activity Log Builder": Sets the reference title for the activity log entry.Log(): Logs the activity entry that has been built using the methods of this codeunit.Query(TableNo: Integer; RecSystemId: Guid): Text+ BC28: Retrieves the activity log entries for the specified table and system identifier as a JSON string.
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 3112 “Activity Log Builder Impl.” (8 calls:
Init → Init,Log → Log,Query → Query, …)
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: "Activity Log Builder"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.