Page 4 "Payment Terms"
Base Application · Microsoft.Foundation.PaymentTerms
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Foundation.PaymentTerms · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Payment Terms |
| SourceTable | Payment Terms |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | Basic, Suite |
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 payment terms. from the table field |
| Due Date Calculation | Due Date Calculation | Specifies a formula that determines how to calculate the due date, for example, when you create an invoice. from the table field | |
| Discount Date Calculation | Discount Date Calculation | Specifies the date formula if the payment terms include a possible payment discount. from the table field | |
| Discount % | Discount % | Specifies the percentage of the invoice amount (amount including VAT is the default setting) that will constitute a possible payment discount. from the table field | |
| Calc. Pmt. Disc. on Cr. Memos | Calc. Pmt. Disc. on Cr. Memos | Specifies that a payment discount, cash discount, cash discount date, and due date are calculated on credit memos with these payment terms. from the table field | |
| Description | Description | Specifies an explanation of the payment terms. from the table field | |
| Coupled to Dataverse | CDSIsCoupledToRecord |
Specifies that the payment term is coupled to a payment term in Dataverse. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Translation | View or edit descriptions for each payment method in different languages. | Page 756 “Payment Term Translations” |
| Dataverse | Synchronize | Send or get updated data to or from Dataverse. | |
| Coupling | Set Up Coupling | Create or modify the coupling to a Dataverse Payment Terms. | |
| Match-Based Coupling | Couple payment terms in Dataverse based on criteria. | ||
| Delete Coupling | Delete the coupling to a Dataverse Payment Terms. | ||
| Dataverse | Synchronization Log | View integration synchronization jobs for the payment terms table. |
Triggers
OnAfterGetRecord, OnOpenPage
Relations
- source table Table 3 “Payment Terms”
Pages and codeunits on this table
- Table 3 “Payment Terms” (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 5330 “CRM Integration Management” (1 call:
OnOpenPage → IsCDSIntegrationEnabled)
Documented on Microsoft Learn
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: "Payment Terms"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.