BC Observatoryunofficial, made by waldo
tableIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table 5396 "CDS Teamroles"

Base Application · Microsoft.Integration.D365Sales

Open in Claude5396.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Table 5359 "CRM Team" (relates to)CRM TeamTable 5389 "CRM Role" (relates to)CRM Role

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

Properties

Property Value
TableType CRM
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 TeamRoleId Guid — DataClassification SystemMetadata
2 RoleId Guid — TableRelation Table 5389 “CRM Role” (CRM Role); DataClassification EndUserPseudonymousIdentifiers
3 VersionNumber BigInteger — DataClassification SystemMetadata
4 TeamId Guid — TableRelation Table 5359 “CRM Team” (CRM Team); DataClassification EndUserPseudonymousIdentifiers

Keys

  • Key1: TeamRoleId (clustered)

Relations

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

Evidence 1 sources