tableRelationship Managementofficial - Microsoftderived - from the source, no model textobsolete - pending

Table 7107 "O365 Contact"

Base Application · Microsoft.CRM.Outlook

Across versionsobsolete pending since 29.0

  1. BC23-27not present
  2. BC28added
  3. BC29-30unchanged

Base Application · Microsoft.CRM.Outlook · captioned “O365 Contacts” · BC28-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption O365 Contacts
TableType Temporary
DataClassification CustomerContent
ObsoleteState Pending
ObsoleteTag 29.0
ObsoleteReason Removed due to Contact Sync redesign, will be deleted in future release.

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 Contact ID Text[250] —
3 Given Name Text[50] —
4 Surname Text[50] —
5 Email Address Text[250] —
6 Business Phone Text[30] —
7 Mobile Phone Text[30] —
8 Job Title Text[100] —
9 Company Name Text[100] —
11 Created DateTime DateTime Created Date Time caption
12 Last Modified DateTime DateTime Last Modified Date Time caption
14 Categories Text[250] —
15 Middle Name Text[50] —
16 Initials Text[10] —
17 Home Phone Text[30] —
18 Fax No. Text[30] —
19 Home Page Text[80] —
20 Email 2 Text[250] —
22 Address Text[100] —
23 Address 2 Text[50] —
24 City Text[50] —
26 Post Code Text[20] —
27 Country/Region Code Code[10] —
28 Display Name Text[50] —

Keys

  • PK: Contact ID (clustered)

Deprecations

  • object: Pending 29.0 (#if not CLEAN29), “Removed due to Contact Sync redesign, will be deleted in future release.”

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: "table", object_name: "O365 Contact"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources