Page 6119 "E-Doc. File Content API"
EDocument · Microsoft.eServices.EDocument.API
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.eServices.EDocument.API · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | E-Doc. File Content API Buffer |
| PageType | API |
| Permissions | tabledata “E-Document” = r, tabledata “E-Document Service” = r, tabledata “E-Doc. File Content API Buffer” = rimd |
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 |
|---|---|---|---|
| General | systemId | Rec.SystemId |
— |
| edocumentEntryNumber | E-Doc Entry No. | Specifies the unique identifier of the E-Document from the table field | |
| edocumentServiceCode | E-Document Service Code | Specifies the service code of the E-Document from the table field | |
| fileContent | Content | Specifies the file contents of the E-Document from the table field |
Procedures
2 local procedures, no public ones.
Triggers
OnFindRecord
Relations
- source table Table 6130 “E-Doc. File Content API Buffer”
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: "E-Doc. File Content API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.