Table 8903 "Email Recipient"
System Application · System.Email
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
System Application · System.Email · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
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 | Email Message Id | Guid | — | TableRelation Table 8900 “Email Message” (“Email Message”.Id); DataClassification SystemMetadata |
| 2 | Email Address | Text[250] | — | DataClassification CustomerContent |
| 3 | Email Recipient Type | Enum “Email Recipient Type” | — | enum Enum 8901 “Email Recipient Type”; DataClassification SystemMetadata |
Keys
- PK: Email Message Id, Email Address, Email Recipient Type (clustered)
Trigger event subscribers
- OnBeforeDeleteEvent: Codeunit 8905 “Email Message Impl.” OnBeforeDeleteRecipient
- OnBeforeInsertEvent: Codeunit 8905 “Email Message Impl.” OnBeforeInsertRecipient
Relations
- Email Message Id: TableRelation Table 8900 “Email Message”
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: "Email Recipient"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.