Codeunit 6752 "Reminder Automation Log Errors"

Base Application · Microsoft.Sales.Reminder · BC24-30 · source at ea08af5e · facts from BC29

Procedures

• LogLastError(ReminderErrorType: Enum "Reminder Automation Error Type"): Logs the last system error that occurred during reminder automation processing.
• LogError(ErrorMessage: Text; ErrorCallstack: Text; ReminderErrorType: Enum "Reminder Automation Error Type"): Creates an error log entry with the specified error message and call stack information.
• Initialize(ReminderAction: Record "Reminder Action"): Initializes the error logging context with the specified reminder action for the current run.

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 6751 “Reminder Action Progress” (1 call: Initialize → GetLastEntryForGroup)

Called by

• Codeunit 6753 “Send Reminder Event Handler” (2 calls: SetGlobalReminderAction → Initialize, UpdateStatusAfterEmailSent → LogLastError)
• Codeunit 6754 “Send Reminder Action Job” (2 calls: Initialize → Initialize, RunSendReminder → LogLastError)
• Codeunit 6757 “Issue Reminder Action Job” (2 calls: Initialize → Initialize, RunIssueReminder → LogLastError)
• Codeunit 6759 “Create Reminders Action Job” (2 calls: CreateReminderForCustomer → LogLastError, Initialize → Initialize)

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: "Reminder Automation Log Errors"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.