tableRelationship Managementofficial - Microsoftderived - from the source, no model text

Table 5100 "Communication Method"

Base Application · Microsoft.CRM.Contact

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC284 fields changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 5050 "Contact" (relates to)ContactPage 5145 "Contact Through" (pages and codeunits on it)Contact Through

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.Contact · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Communication Method
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 Key Integer —
2 Description Δ BC28 Text[100] Specifies the description of the phone number or e-mail address.
3 Number Δ BC28 Text[30] Specifies the telephone number.
4 Contact No. Code[20] — TableRelation Table 5050 “Contact”
5 Name Text[100] —
6 Type Δ BC28 Enum “Contact Type” Specifies the type of the contact to which the phone number is related. There are two options: enum Enum 5050 “Contact Type”
7 E-Mail Δ BC28 Text[80] Specifies the contact’s email address.

Keys

  • Key1: Key (clustered)

Relations

Pages and codeunits on this 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: "Communication Method"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources