codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 3111 "Activity Log Builder"

System Application · System.Log

Across versions

  1. BC23-25not present
  2. BC26added
  3. BC271 procedures added
  4. BC281 procedures added
  5. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 3112 "Activity Log Builder Impl." (calls, 8 links)Activity Log Builder Impl.

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.

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 activities
  • SetConfidence(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.

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.

Evidence 1 sources