codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 545 "Send Reminder"

Base Application · Microsoft.Sales.Reminder

Across versions

  1. BC23not present
  2. BC24added
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 6753 "Send Reminder Event Handler" (calls, 2 links)Send Reminder Event Handler

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.

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

Properties

Property Value
Permissions tabledata “Issued Reminder Header” = rmid, tabledata “Email Outbox” = rmid

Event subscriptions

  • HandleEmailSent subscribes to Codeunit “Document-Mailing” OnAfterEmailSent
  • ClearEmailFields subscribes to Table “Issued Reminder Header” OnBeforeModifyEvent

Procedures

  • UpdateReminderSentFromUI(var IssuedReminderHeader: Record "Issued Reminder Header"): Prompts the user to select how the reminder was sent and updates the sent email fields accordingly.
  • UpdateSentEmailFields(var IssuedReminderHeader: Record "Issued Reminder Header"): Updates the email tracking fields on the issued reminder header after successful email delivery.
  • UpdateSentForCurrentLevelWithoutEmail(var IssuedReminderHeader: Record "Issued Reminder Header"): Marks the reminder as sent for the current level without recording email delivery details.
  • SetFailedOutboxMessageID(MessageID: BigInteger; IssuedReminderNo: Code[20]): Stores the failed email outbox message ID on the issued reminder header for later retry.
  • DeleteFailedOutboxMessageIfExists(IssuedReminderNo: Code[20]): Deletes the failed email outbox message linked to the issued reminder if it exists.

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.

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

Evidence 1 sources