Page 8050 "Sales Person API"
Subscription Billing
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
Subscription Billing · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Salesperson/Purchaser |
| PageType | API |
| 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 | systemId | Rec.SystemId |
— |
| code | Code | Specifies a code for the salesperson or purchaser. from the table field | |
| name | Name | Specifies the name of the salesperson or purchaser. from the table field |
Relations
- source table Table 13 “Salesperson/Purchaser”
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 Person API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.