Table 5106 "Interaction Merge Data"
Base Application · Microsoft.CRM.Interaction
Across versions
- BC23present
- BC244 fields changed
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.CRM.Interaction · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| 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 | ID Δ BC24 | Guid | — | |
| 2 | Contact No. Δ BC24 | Code[20] | — | TableRelation Contact.“No.” |
| 3 | Salesperson Code Δ BC24 | Code[20] | — | TableRelation Table 13 “Salesperson/Purchaser” (“Salesperson/Purchaser”.Code) |
| 4 | Log Entry Number Δ BC24 | Integer | — | TableRelation Table 5065 “Interaction Log Entry” (“Interaction Log Entry”.“Entry No.”) |
Keys
- PK: ID (clustered)
Relations
- Salesperson Code: TableRelation Table 13 “Salesperson/Purchaser”
- Log Entry Number: TableRelation Table 5065 “Interaction Log Entry”
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: "Interaction Merge Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.