Page 1160 "Sales Documents"
Base Application · Microsoft.Sales.Receivables
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Sales.Receivables · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Sales Documents |
| SourceTable | Cust. Ledger Entry |
| PageType | ListPart |
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 | Due Date | Due Date | Specifies when the sales documents are due. |
| Document Type | Document Type | Specifies the type of sales document. | |
| Document No. | Document No. | Specifies the sales document number. | |
| Customer Name | CustomerName |
Specifies customer name. | |
| Remaining Amount | Remaining Amount | Specifies the amount that remains to be paid on the sales documents. |
Events published
OnAfterOnAfterGetRecord(CustLedgerEntry: Record "Cust. Ledger Entry"; var StyleTxt: Text)(integration)
Procedures
SetFilterForOverdueSalesInvoiceAmount()SetFilterForSalesDocsDueToday()SetFilterForSalesDocsDueNextWeek()
Triggers
OnAfterGetRecord, OnOpenPage
Relations
- source table Table 21 “Cust. Ledger Entry”
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: "page", object_name: "Sales Documents"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.