Page 171 "Standard Sales Code Subform"
Base Application · Microsoft.Sales.Document
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC261 events added
- BC27unchanged
- BC281 procedures changed
- BC29-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Document · captioned “Lines” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Lines |
| SourceTable | Standard Sales Line |
| 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 |
|---|---|---|---|
| Control1 | Type | Type | Specifies whether the line is for a general ledger account, item, resource, fixed asset or item charge. from the table field |
| Type | TypeAsText |
Specifies whether the line is for a general ledger account, item, fixed asset or item charge. | |
| No. | No. | Specifies the number of a general ledger account, item, resource, additional cost, or fixed asset, depending on the contents of the Type field. from the table field | |
| Variant Code | Variant Code | Specifies the variant of the item on the line. from the table field | |
| Description | Description | Specifies a description of the entry, which is based on the contents of the Type and No. fields. from the table field | |
| Quantity | Quantity | Specifies the number of units of the item on the line. from the table field | |
| Unit of Measure Code | Unit of Measure Code | Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted. from the table field | |
| Amount Excl. VAT | Amount Excl. VAT | Specifies the net amount for the standard sales line. This field only applies to lines of type G/L Account and Charge (Item). from the table field | |
| Shortcut Dimension 1 Code | Shortcut Dimension 1 Code | Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field | |
| Shortcut Dimension 2 Code | Shortcut Dimension 2 Code | Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field | |
| ShortcutDimCode[3] | ShortcutDimCode[3] |
— | |
| ShortcutDimCode[4] | ShortcutDimCode[4] |
— | |
| ShortcutDimCode[5] | ShortcutDimCode[5] |
— | |
| ShortcutDimCode[6] | ShortcutDimCode[6] |
— | |
| ShortcutDimCode[7] | ShortcutDimCode[7] |
— | |
| ShortcutDimCode[8] | ShortcutDimCode[8] |
— |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Line | Dimensions | View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history. |
Events published
OnValidateDescriptionOnBeforeChangeSalesLineType(var StandardSalesLine: Record "Standard Sales Line"; var IsHandled: Boolean)+ BC26 (integration)
Procedures
UpdateTypeText()Δ BC28: Updates the display text for the Type field based on the current record value.
Plus 2 local procedures.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnInit, OnNewRecord, OnInsertRecord, OnOpenPage
Relations
- source table Table 171 “Standard Sales Line”
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 9179 “Application Area Mgmt. Facade” (3 calls:
OnInit → IsFoundationEnabled,OnNewRecord → IsAdvancedEnabled,OnNewRecord → IsFoundationEnabled) - Codeunit 408 “DimensionManagement” (1 call:
SetDimensionsVisibility → UseShortcutDims)
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: "Standard Sales Code Subform"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.