Page 5150 "Contact Segment List"
Base Application · Microsoft.CRM.Segment
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.CRM.Segment · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Contact Segment List |
| SourceTable | Segment Line |
| 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 | Segment No. | Segment No. | Specifies the number of the segment to which this segment line belongs. |
| Description | Description | Specifies the description of the segment line. from the table field | |
| Date | Date | Specifies the date the segment line was created. | |
| Contact No. | Contact No. | Specifies the number of the contact to which this segment line applies. from the table field | |
| Contact Name | Contact Name | Specifies the name of the contact to which the segment line applies. The program automatically fills in this field when you fill in the Contact No. field on the line. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Segment | Card | View detailed information about the contact segment. | Page 5091 “Segment” |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord
Relations
- source table Table 5077 “Segment 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 4030 “Client Type Management” (1 call:
GetCaption → GetCurrentClientType)
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 Segment List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.