Page 431 "Reminder Terms"
Base Application · Microsoft.Sales.Reminder
Across versionsobsolete pending since 29.0
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Sales.Reminder · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Reminder Terms |
| SourceTable | Reminder Terms |
| PageType | List |
| UsageCategory | None |
| ApplicationArea | Basic, Suite |
| ObsoleteState | Pending |
| ObsoleteTag | 29.0 |
| ObsoleteReason | Use page 837 “Reminder Terms List” 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 | Code | Code | Specifies a code to identify this set of reminder terms. from the table field |
| Description | Description | Specifies a description of the reminder terms. from the table field | |
| Max. No. of Reminders | Max. No. of Reminders | Specifies the maximum number of reminders that can be created for an invoice. from the table field | |
| Post Interest | Post Interest | Specifies whether or not any interest listed on the reminder should be posted to the general ledger and customer accounts. | |
| Post Additional Fee | Post Additional Fee | Specifies whether or not any additional fee listed on the reminder should be posted to the general ledger and customer accounts. | |
| Post Add. Fee per Line | Post Add. Fee per Line | Specifies whether or not any additional fee listed on the finance charge memo should be posted to the general ledger and customer accounts when the memo is issued. | |
| Minimum Amount (LCY) | Minimum Amount (LCY) | Specifies the minimum amount for which a reminder will be created. | |
| Note About Line Fee on Report | Note About Line Fee on Report | Specifies that any notes about line fees will be added to the reminder. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Levels | View the reminder levels that are used to define when reminders can be created and what charges and texts they must include. | Page 432 “Reminder Levels” |
| Translation | View the reminder text in any other languages that are set up for reminders. | Page 1052 “Reminder Terms Translation” |
Triggers
OnOpenPage
Relations
- source table Table 292 “Reminder Terms”
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.
- Page 837 “Reminder Terms List” (1 call:
OnOpenPage → (object))
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 837 “Reminder Terms List” 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 Terms"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.