Table 8911 "Email Scenario Attachments"
System Application · System.Email
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
System Application · System.Email · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 8896 “Email Choose Scenario Attach” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Access | Public |
| Extensible | true |
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 | BigInteger | — | AutoIncrement; DataClassification SystemMetadata |
| 2 | Scenario | Enum “Email Scenario” | Specifies which Email Scenario the attachment comes from. via Page 8896 “Email Choose Scenario Attach” | enum Enum 8890 “Email Scenario”; DataClassification SystemMetadata |
| 3 | Attachment Name | Text[250] | Specifies the name of the attachment via Page 8896 “Email Choose Scenario Attach” | DataClassification CustomerContent |
| 4 | Email Attachment | Media | — | DataClassification CustomerContent |
| 5 | AttachmentDefaultStatus | Boolean | — | TableRelation Table 8913 “Email Attachments” (“Email Attachments”.AttachmentDefaultStatus); DataClassification SystemMetadata |
Keys
- PK: Id (clustered)
- Scenario: Scenario, Attachment Name
Relations
- AttachmentDefaultStatus: TableRelation Table 8913 “Email Attachments”
Pages and codeunits on this table
- Page 8896 “Email Choose Scenario Attach” (source 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: "Email Scenario Attachments"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.