Table 8913 "Email 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 8897 “Email Scenario Attach Setup” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Access | Public |
| TableType | Temporary |
| Permissions | tabledata “Email Scenario Attachments” = r |
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 the email scenario that the attachment came from. Attachments set as default for email scenarios are automatically attached to emails that are sent from processes related to the scenario. via Page 8897 “Email Scenario Attach Setup” | enum Enum 8890 “Email Scenario”; DataClassification SystemMetadata |
| 3 | Attachment Name | Text[250] | Specifies the name of the attachment via Page 8897 “Email Scenario Attach Setup” | DataClassification CustomerContent |
| 4 | Email Attachment | Media | — | DataClassification CustomerContent |
| 5 | AttachmentDefaultStatus | Boolean | Specifies whether to automatically attach the file to emails sent from processes related to this scenario. You can manually attach files that are not default. via Page 8897 “Email Scenario Attach Setup” | DataClassification SystemMetadata |
Keys
- PK: Id (clustered)
- Scenario: Scenario, Attachment Name
Referenced by
1 fields in 1 objects relate to this table (TableRelation or CalcFormula).
- Table 8911 “Email Scenario Attachments”: AttachmentDefaultStatus
Pages and codeunits on this table
- Page 8897 “Email Scenario Attach Setup” (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 Attachments"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.