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

Table 5084 "Team Salesperson"

Base Application · Microsoft.CRM.Team

Across versions

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

Neighbourhood 4 connected objects and pages

Table 13 "Salesperson/Purchaser" (relates to, 2 links)Salesperson/PurchaserTable 5083 "Team" (relates to, 2 links)TeamPage 5106 "Team Salespeople" (pages and codeunits on it)Team SalespeoplePage 5107 "Salesperson Teams" (pages and codeunits on it)Salesperson Teams

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

Properties

Property Value
Caption Team Salesperson
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 Team Code Δ BC28 Code[10] Specifies the code of the team to which the salesperson belongs. TableRelation Table 5083 “Team”; NotBlank
2 Salesperson Code Δ BC28 Code[20] Specifies the code of the salesperson you want to register as part of the team. TableRelation Table 13 “Salesperson/Purchaser” (Salesperson/Purchaser); NotBlank
3 Team Name Δ BC24 Δ BC28 Text[50] Specifies the name of the team. FlowField: lookup(Team.Name where(Code = field(“Team Code”))); not editable
4 Salesperson Name Δ BC24 Δ BC28 Text[50] Specifies the name of the salesperson you want to register as part of the team. FlowField: lookup(“Salesperson/Purchaser”.Name where(Code = field(“Salesperson Code”))); not editable

Keys

  • Key1: Team Code, Salesperson Code (clustered)
  • Key2: Salesperson Code

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

Evidence 1 sources