Table 5098 "Saved Segment Criteria"
Base Application · Microsoft.CRM.Segment
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC284 fields changed
- BC29-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.CRM.Segment · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Saved Segment Criteria |
| DataClassification | CustomerContent |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Code Δ BC28 | Code[10] | Specifies the code of the saved segment criteria. | NotBlank |
| 2 | Description Δ BC28 | Text[100] | Specifies the description of the saved segment criteria. | |
| 4 | User ID Δ BC28 | Code[50] | Specifies the ID of the user who posted the entry, to be used, for example, in the change log. | TableRelation User.“User Name”; not editable; DataClassification EndUserIdentifiableInformation |
| 5 | No. of Actions Δ BC28 | Integer | Specifies the number of actions that make up the segment criteria. | FlowField: count(“Saved Segment Criteria Line” where(“Segment Criteria Code” = field(Code), Type = const(Action))); not editable |
Keys
- Key1: Code (clustered)
Triggers
OnDelete, OnInsert
Relations
- lookup page Page 5141 “Saved Segment Criteria List”
- No. of Actions: CalcFormula Table 5099 “Saved Segment Criteria Line”
Referenced by
1 fields in 1 objects relate to this table (TableRelation or CalcFormula).
- Table 5099 “Saved Segment Criteria Line”: Segment Criteria Code
Pages and codeunits on this table
- Page 5140 “Saved Segment Criteria Card” (source table)
- Page 5141 “Saved Segment Criteria List” (source table)
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: "table", object_name: "Saved Segment Criteria"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.