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

Table 7030 "Campaign Target Group"

Base Application · Microsoft.CRM.Campaign

Across versions

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

Neighbourhood 4 connected objects and pages

Table 18 "Customer" (relates to)CustomerTable 5050 "Contact" (relates to)ContactTable 5071 "Campaign" (relates to)CampaignTable 5071 "Campaign" (referenced by)Campaign

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

Properties

Property Value
Caption Campaign Target Group
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 Type Option — OptionCaption: Customer,Contact
2 No. Code[20] — TableRelation Table 18 “Customer”, Table 5050 “Contact” (if (Type = const(Customer)) Customer else if (Type = const(Contact)) Contact where(Type = filter(Company)))
3 Campaign No. Code[20] — TableRelation Table 5071 “Campaign”

Keys

  • Key1: Type, No., Campaign No. (clustered)
  • Key2: Campaign No.
  • Key3: No.

Procedures

  • CopyTo(var TempCampaignTargetGroup: Record "Campaign Target Group" temporary): Boolean

Relations

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

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

Evidence 1 sources