Page 2123 "O365 Incoming Doc. Att. Pict."
Base Application · Microsoft.EServices.EDocument
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.EServices.EDocument · captioned “Attachment Picture” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Attachment Picture |
| SourceTable | Incoming Document Attachment |
| PageType | Card |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Content | AttachmentContent | Content | Specifies the content of the attachment. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Remove attachment | — |
Triggers
OnAfterGetRecord
Relations
- source table Table 133 “Incoming Document Attachment”
Recent changes
- 2026-09-07 #11036 Ruleset hardening: promote four compatibility rules to Error (main, BC30, other)
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: "page", object_name: "O365 Incoming Doc. Att. Pict."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.