Page 20023 "APIV1 - Payment Terms"

APIV1 · Microsoft.API.V1 · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	‘paymentTerms’, Locked = true
Extensible	false
SourceTable	Payment Terms
PageType	API

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
Group	id	`Rec.SystemId`	—
	code	Code	Specifies a code to identify this set of payment terms. from the table field
	displayName	Description	Specifies an explanation of the payment terms. from the table field
	dueDateCalculation	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
	discountDateCalculation	Discount Date Calculation	Specifies the date formula if the payment terms include a possible payment discount. from the table field
	discountPercent	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
	calculateDiscountOnCreditMemos	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
	lastModifiedDateTime	Last Modified Date Time	—

Procedures

1 local procedures, no public ones.

Triggers

OnInsertRecord, OnModifyRecord

Relations

source table Table 3 “Payment 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.

Codeunit 5465 “Graph Mgt - General Tools” (1 call: OnInsertRecord → ProcessNewRecordFromAPI)

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: "APIV1 - Payment Terms"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.