BC Observatoryunofficial, made by waldo
tableRelationship Managementofficial - Microsoftderived - from the source, no model text

Table 5078 "Segment History"

Base Application · Microsoft.CRM.Segment

Open in Claude5078.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Table 5050 "Contact" (relates to)ContactTable 5076 "Segment Header" (relates to)Segment Header

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.CRM.Segment · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Segment History
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 Segment No. Code[20] — TableRelation Table 5076 “Segment Header” (Segment Header)
2 Segment Action No. Integer —
3 Segment Line No. Integer —
4 Contact No. Code[20] — TableRelation Table 5050 “Contact”
5 Action Taken Option — OptionCaption: Insertion,Deletion

Keys

  • Key1: Segment No., Segment Action No., Segment Line No. (clustered)

Relations

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: "Segment History"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources