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

Table 5060 "Contact Web Source"

Base Application · Microsoft.CRM.Contact

Across versions

  1. BC23present
  2. BC242 fields changed
  3. BC25-27unchanged
  4. BC283 fields changed
  5. BC29-30unchanged

Neighbourhood 4 connected objects and pages

Table 5050 "Contact" (relates to, 2 links)ContactTable 5059 "Web Source" (relates to, 2 links)Web SourcePage 5070 "Contact Web Sources" (pages and codeunits on it, 2 links)Contact Web SourcesPage 5071 "Web Source Launch" (pages and codeunits on it)Web Source Launch

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 Contact Web Source
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 Contact No. Code[20] — TableRelation Table 5050 “Contact” (Contact where(Type = const(Company))); NotBlank
2 Web Source Code Δ BC28 Code[10] Specifies the Web source code. This field is not editable. TableRelation Table 5059 “Web Source” (Web Source); NotBlank
3 Search Word Δ BC28 Text[30] Specifies the search word to search for information about the contact on the Internet.
4 Web Source Description Δ BC24 Δ BC28 Text[100] Specifies the description of the Web source you have assigned to the contact. FlowField: lookup(“Web Source”.Description where(Code = field(“Web Source Code”))); not editable
5 Contact Name Δ BC24 Text[100] — FlowField: lookup(Contact.Name where(“No.” = field(“Contact No.”))); not editable

Keys

  • Key1: Contact No., Web Source Code (clustered)

Procedures

  • Launch()

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

Evidence 1 sources