Table 293 "Reminder Level"
Base Application · Microsoft.Sales.Reminder
Across versions
- BC23present
- BC242 fields added
- BC25-27unchanged
- BC289 fields changed
- BC29-30unchanged
Neighbourhood 14 connected objects and pages
Base Application · Microsoft.Sales.Reminder · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 432 “Reminder Levels” (3 Learn pages).
Properties
| Property | Value |
|---|---|
| Caption | Reminder Level |
| 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 | Reminder Terms Code Δ BC28 | Code[10] | Specifies the reminder terms code for the reminder. | TableRelation Table 292 “Reminder Terms” (Reminder Terms); NotBlank |
| 2 | No. Δ BC28 | Integer | Specifies the number of the involved entry or record, according to the specified number series. | NotBlank |
| 3 | Grace Period Δ BC28 | DateFormula | Specifies the length of the grace period for this reminder level. | |
| 4 | Additional Fee (LCY) Δ BC28 | Decimal | Specifies the amount of the additional fee in LCY that will be added on the reminder. via Page 1895 “Reminder Level Fee Setup” | |
| 5 | Calculate Interest Δ BC28 | Boolean | Specifies whether interest should be calculated on the reminder lines. | |
| 6 | Due Date Calculation Δ BC28 | DateFormula | Specifies a formula that determines how to calculate the due date on the reminder. | |
| 7 | Add. Fee per Line Amount (LCY) Δ BC28 | Decimal | Specifies the line amount of the additional fee in LCY. via Page 1895 “Reminder Level Fee Setup” | |
| 8 | Add. Fee per Line Description Δ BC28 | Text[100] | Specifies a description of the additional fee. | |
| 9 | Add. Fee Calculation Type Δ BC28 | Option | Specifies how the additional fee is calculated. Fixed: The Additional Fee values on the line on the Reminder Levels page are used. Dynamics Single: The per-line values on the Additional Fee Setup page are used. Accumulated Dynamic: The values on the Additional Fee Setup page are used. | OptionCaption: Fixed,Single Dynamic,Accumulated Dynamic |
| 20 | Reminder Attachment Text + BC24 | Guid | — | TableRelation Table 502 “Reminder Attachment Text” (“Reminder Attachment Text”.Id) |
| 21 | Reminder Email Text + BC24 | Guid | — | TableRelation Table 503 “Reminder Email Text” (“Reminder Email Text”.Id) |
Keys
- Key1: Reminder Terms Code, No. (clustered)
Procedures
CalculateAdditionalFixedFee(CurrencyCode: Code[10]; ChargePerLine: Boolean; PostingDate: Date): Decimal: Calculates the fixed additional fee amount for this reminder level in the specified currency.NewRecord(): Initializes the level number for a new record to be one higher than the last level.GetAdditionalFee(RemainingAmount: Decimal; CurrencyCode: Code[10]; ChargePerLine: Boolean; PostingDate: Date): Decimal: Gets the additional fee amount based on the fee calculation type and remaining amount.
Triggers
OnDelete, OnRename
Relations
- drill-down page Page 432 “Reminder Levels”
- lookup page Page 432 “Reminder Levels”
- Reminder Terms Code: TableRelation Table 292 “Reminder Terms”
- Reminder Attachment Text: TableRelation Table 502 “Reminder Attachment Text”
- Reminder Email Text: TableRelation Table 503 “Reminder Email Text”
Referenced by
4 fields in 4 objects relate to this table (TableRelation or CalcFormula).
- Table 1050 “Additional Fee Setup”: Reminder Level No.
- Table 294 “Reminder Text”: Reminder Level
- Table 295 “Reminder Header”: Reminder Level
- Table 297 “Issued Reminder Header”: Reminder Level
Pages and codeunits on this table
- Page 1895 “Reminder Level Fee Setup” (source table)
- Page 1896 “Reminder Level Setup” (source table)
- Page 432 “Reminder Levels” (source table)
- Page 835 “Reminder Level Communication” (source table)
Recent changes
- 2026-08-31 #10504 [Reminders] Complete the communication texts model uptake (main, BC30, feature)
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 Level"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.