Page 8061 "Item Serv. Commitment Packages"
Subscription Billing · Microsoft.SubscriptionBilling
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
Subscription Billing · Microsoft.SubscriptionBilling · captioned “Item Subscription Packages” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Item Subscription Packages |
| SourceTable | Item Subscription Package |
| PageType | List |
| UsageCategory | None |
| ApplicationArea | All |
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 |
|---|---|---|---|
| General | Code | Code | Specifies a code to identify this Subscription Package. |
| Description | Description | Specifies a description of the Subscription Package. | |
| Standard | Standard | Specifies whether the package Subscription Lines should be automatically added to the sales process when the item is sold. If the checkbox is not set, the package Subscription Lines can be added manually in the sales process. | |
| Price Group | Price Group | Specifies the customer price group that will be used for the invoicing of Subscription Lines. | |
| Content | PackageLines | part Page 8058 “Service Comm. Package Lines” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Show all or single package(s) | Toggle visibility of package lines to a single package or to all packages. |
Events published
OnBeforeCodeLookup(var SubscriptionPackage: Record "Subscription Package"; CurrentItemNo: Code[20])(integration)
Triggers
OnOpenPage, OnNewRecord, OnInsertRecord, OnDeleteRecord, OnAfterGetCurrRecord
Relations
- source table Table 8058 “Item Subscription Package”
Pages and codeunits on this table
- Table 8058 “Item Subscription Package” (drill-down page)
- Table 8058 “Item Subscription Package” (lookup page)
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). 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: "Item Serv. Commitment Packages"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.