Page 5145 "Contact Through"
Base Application · Microsoft.CRM.Contact
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.CRM.Contact · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Contact Through |
| SourceTable | Communication Method |
| PageType | List |
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 the type of the contact to which the phone number is related. There are two options: from the table field |
| Description | Description | Specifies the description of the phone number or e-mail address. from the table field | |
| Number | Number | Specifies the telephone number. from the table field | |
| Specifies the contact’s email address. from the table field |
Triggers
OnInit, OnOpenPage
Relations
- source table Table 5100 “Communication Method”
Extended by
Called by
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 397 “Mail” (1 call:
CollectAddresses → (object)) - Codeunit 5053 “TAPIManagement” (1 call:
ShowNumbers → (object))
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: "Contact Through"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.