Page 432 "Reminder Levels"
Base Application · Microsoft.Sales.Reminder
Across versionsobsolete pending since 29.0
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Sales.Reminder · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Reminder Levels |
| SourceTable | Reminder Level |
| PageType | List |
| ObsoleteState | Pending |
| ObsoleteTag | 29.0 |
| ObsoleteReason | Use page 1896 “Reminder Level Setup” instead. |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Reminder Terms Code | Reminder Terms Code | Specifies the reminder terms code for the reminder. from the table field |
| No. | No. | Specifies the number of the involved entry or record, according to the specified number series. from the table field | |
| Grace Period | Grace Period | Specifies the length of the grace period for this reminder level. from the table field | |
| Due Date Calculation | Due Date Calculation | Specifies a formula that determines how to calculate the due date on the reminder. from the table field | |
| Calculate Interest | Calculate Interest | Specifies whether interest should be calculated on the reminder lines. from the table field | |
| Additional Fee (LCY) | Additional Fee (LCY) | Specifies the amount of the additional fee in LCY that will be added on the reminder. | |
| Add. Fee per Line Amount (LCY) | Add. Fee per Line Amount (LCY) | Specifies the line amount of the additional fee. | |
| Add. Fee Calculation Type | Add. Fee Calculation Type | 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. from the table field | |
| Add. Fee per Line Description | Add. Fee per Line Description | Specifies a description of the additional fee. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Level | Beginning Text | Define a beginning text for each reminder level. The text will then be printed on the reminder. | Page 433 “Reminder Text” |
| Ending Text | Define an ending text for each reminder level. The text will then be printed on the reminder. | Page 433 “Reminder Text” | |
| Currencies | View or edit additional feed in additional currencies. | Page 478 “Currencies for Reminder Level” | |
| Setup | Additional Fee | View or edit the fees that apply to late payments. | Page 1050 “Additional Fee Setup” |
| Additional Fee per Line | View or edit the fees that apply to late payments. | Page 1050 “Additional Fee Setup” | |
| View Additional Fee Chart | View additional fees in a chart. |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnNewRecord, OnOpenPage
Relations
- source table Table 293 “Reminder Level”
Pages and codeunits on this table
- Table 293 “Reminder Level” (drill-down page)
- Table 293 “Reminder Level” (lookup page)
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 4030 “Client Type Management” (1 call:
OnOpenPage → GetCurrentClientType)
Recent changes
- 2026-08-31 #10504 [Reminders] Complete the communication texts model uptake (main, BC30, feature)
Documented on Microsoft Learn
- Set Up Multiple Interest Rates for Delayed Payment
- Set Up Reminder Terms and Levels
- Send Reminders of Outstanding Balances
Deprecations
- object: Pending 29.0 (#if not CLEAN29), “Use page 1896 “Reminder Level Setup” instead.”
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). 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: "page", object_name: "Reminder Levels"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.