Page 9084 "Customer Details FactBox"
Base Application · Microsoft.Sales.Customer
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Customer · captioned “Customer Details” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Customer Details |
| SourceTable | Customer |
| PageType | CardPart |
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 |
|---|---|---|---|
| Content | Customer No. | No. | Specifies the number of the customer. The field is either filled automatically from a defined number series, or you enter the number manually because you have enabled manual number entry in the number-series setup. from the table field |
| Name | Name | Specifies the customer’s name that appears on all related documents. For companies, specify the company’s name here, and then add the relevant people as contacts that you link to this customer. from the table field | |
| Phone No. | Phone No. | Specifies the customer’s telephone number. from the table field | |
| Specifies the customer’s email address. from the table field | |||
| Fax No. | Fax No. | Specifies the customer’s fax number. from the table field | |
| Credit Limit (LCY) | Credit Limit (LCY) | Specifies the maximum amount of credit that you extend to the customer for their purchases before you issue warnings. The value 0 represents unlimited credit. from the table field | |
| Available Credit (LCY) | Rec.CalcAvailableCreditUI() |
Specifies a customer’s available credit. If the available credit is 0 and the customer’s credit limit is also 0, then the customer has unlimited credit because no credit limit has been defined. | |
| Payment Terms Code | Payment Terms Code | Specifies a code that indicates the payment terms that you require of the customer. from the table field | |
| Contact | Contact | Specifies the name of the person you regularly contact when you do business with this customer. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Actions | Ship-to Address | View the ship-to address that is specified for the customer. | Page 301 “Ship-to Address List” |
| Comments | View or add comments for the record. | Page 124 “Comment Sheet” |
Events published
OnBeforeShowDetails(var Customer: Record Customer; var IsHandled: Boolean)(integration): Raised before showing the customer card details.
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetRecord
Relations
- source table Table 18 “Customer”
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 21 “Customer Card” (1 call:
ShowDetails → (object))
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: "Customer Details FactBox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.