Page 692 "Report Inbox File API"
Base Application · Microsoft.EServices.EDocument
Across versions
- BC23-28not present
- BC29added
- BC30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.EServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Report Inbox File Buffer |
| PageType | API |
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 |
|---|---|---|---|
| Group | id | Id | — |
| companyName | Company Name | — | |
| fileName | File Name | — | |
| byteSize | Byte Size | — | |
| documentContent | Content | — |
Procedures
1 local procedures, no public ones.
Triggers
OnFindRecord
Relations
- source table Table 476 “Report Inbox File Buffer”
Recent changes
- 2026-08-26 #10631 Integration/main to releases 29.x 31a860b5 (releases/29.x, BC29, feature, added)
- 2026-08-21 #10010 Add Report Inbox API pages for automated report retrieval (main, BC30, feature, added)
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: "Report Inbox File API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.