Page 366 "Electronic Document Formats"
Base Application · Microsoft.Foundation.Reporting
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Foundation.Reporting · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Electronic Document Formats |
| SourceTable | Electronic Document Format |
| PageType | List |
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 | Code | Code | Specifies a code to identify the electronic document format in the system. from the table field |
| Description | Description | Specifies the electronic document format. from the table field |
Triggers
OnOpenPage
Relations
- source table Table 61 “Electronic Document Format”
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: "Electronic Document Formats"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.