Page 6726 "OData EDM Definition Card"
Base Application · System.Integration
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · System.Integration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | OData EDM Definition Card |
| SourceTable | OData Edm Type |
| 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 |
|---|---|---|---|
| General | Key | Rec.Key |
— |
| Description | Rec.Description |
Specifies a description of the Open Data Protocol EDM definition. | |
| EDM Definition XML | EDM Definition XML | ODataEDMXMLTxt |
— |
Procedures
GetEDMXML(): TextSetEDMXML(EDMXml: Text)
Triggers
OnAfterGetRecord
Pages and codeunits on this table
- Page 6725 “OData EDM Definitions” (card page)
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: "OData EDM Definition Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.