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

Table 6752 "Reminder Action Log"

Base Application · Microsoft.Sales.Reminder

Across versions

  1. BC23not present
  2. BC24added
  3. BC251 fields changed
  4. BC261 fields changed
  5. BC271 fields changed
  6. BC284 fields changed
  7. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Page 6757 "Reminder Act. History Log" (pages and codeunits on it)Reminder Act. History LogTable 6753 "Reminder Action Group Log" (referenced by)Reminder Action Group Log

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
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Id Integer — AutoIncrement
2 Run Id Integer —
3 Reminder Action Group ID Code[50] —
4 Reminder Action ID Δ BC28 Code[50] Specifies the reminder action that was performed.
5 Total Records Processed Integer —
6 Total Errors Δ BC25 Δ BC26 Δ BC27 Δ BC28 Integer Specifies the total number of errors that occurred during the action job. obsolete Pending 27.0; #if not CLEANSCHEMA29
7 Last Record Processed RecordId —
10 Status Δ BC28 Enum “Reminder Log Status” Specifies the status of the action. enum Enum 6751 “Reminder Log Status”
11 Status summary Δ BC28 Text[1024] Specifies the details of the last action job.
12 Details Blob —
13 JobQueueID Guid —

Keys

  • Key1: Id (clustered)

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

Recent changes

Deprecations

  • field Total Errors: Pending 27.0 (#if not CLEANSCHEMA29), “This field is obsolete and should not be used.”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). 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: "table", object_name: "Reminder Action Log"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources