Enum 135 "Attachment Entity Buffer Document Type"
Base Application · Microsoft.Integration.Graph
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC28declaration changed
- BC29-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Integration.Graph · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | (blank) | ||
| 1 | Journal | Journal | |
| 9 | Employee | Employee | |
| 11 | Item | Item | |
| 12 | Customer | Customer | |
| 13 | Vendor | Vendor |
Extended by
- Enum extension 5050 “Asm. Doc.Att.Ent.Buf.Doc.Type”
- Enum extension 5051 “Invt.Att.Ent.Buf.Doc.Type”
- Enum extension 5052 “Project Att.Ent.Buf.Doc.Type”
- Enum extension 5053 “Purchase Att.Ent.Buf.Doc.Type”
- Enum extension 5054 “Sales Att.Ent.Buf.Doc.Type”
Implements
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "enum", object_name: "Attachment Entity Buffer Document Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.