Known Issues for OData Support
Learn about known issues with OData support in PowerBuilder.
| CR# | Description |
|---|---|
| 757989 | Updates performed on a primary key in OData DataWindows may miss
some values. The default behavior of updating primary keys in an OData DataWindow is to use Delete and then Insert. If the user changes the primary key of a row and saves the changes, the row is deleted and a new row is inserted, with the changed primary key value and other column values for the edited row. The columns of the table which were not selected in the DataWindow are missed in the row. In DataWindows using other datasources, you can change this default behavior. That option is not available in PowerBuilder 12.6 for DataWindows using an OData datasource. |
| 756525, 756535 | SQL Anywhere update required to use ODataSalesOrder
example. To use the OData example of ODataSalesOrder in PowerBuilder 12.6 with SQL Anywhere, apply the latest EBF for SQL Anywhere 16.0. |
| 752713 | DateTimeOffset datatype and Time datatype are supported as
display-only in OData applications In applications using an OData service, these datatypes are supported only for display. They cannot be used as retrieval arguments. |
| 748612 | No support for OData version 3 or later PowerBuilder 12.6 does not support OData Service version 3 or later. |