Page 5093 "Segment List"
Base Application · Microsoft.CRM.Segment
Across versions
- BC23-30present
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.CRM.Segment · captioned “Segments” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Segments |
| SourceTable | Segment Header |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | RelationshipMgmt |
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 | No. | No. | Specifies the number of the involved entry or record, according to the specified number series. from the table field |
| Description | Description | Specifies the description of the segment. from the table field | |
| Campaign No. | Campaign No. | Specifies the number of the campaign for which the segment has been created. from the table field | |
| Salesperson Code | Salesperson Code | Specifies the code of the salesperson responsible for this segment and/or interaction. from the table field | |
| Date | Date | Specifies the date that the segment was created. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Segment | Tasks | View the tasks that have been assigned to salespeople or teams. Tasks can be linked to contacts and/or campaigns. | Page 5096 “Task List” |
Relations
- card page Page 5091 “Segment”
- source table Table 5076 “Segment Header”
Pages and codeunits on this table
- Table 5076 “Segment Header” (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: "Segment List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.