Changelog
Items listed in bold are considered potentially breaking changes from the previous released version. Potentially breaking changes include:
-
Changes to the structure of returned objects
- Addition/removal of properties or links
- Changes to the structure of composed types (e.g. collections)
- Status code changes
- Changes to default parameter values
We make a special effort not to remove properties or links, change the structure of composed types, change the class of status codes (e.g. 200 class to 400 class), or change default parameter values.
Clients should be prepared to handle changes to status codes within the same class, especially the 400 and 500 classes, and to handle the addition of properties and links to response objects.
PI Web API OMF Services 2019 SP1
New features:
-
Limited support for the
updateaction has been added.updateis now supported fordatarequests for thestatic,dynamic, and__linkresource types.- For more information, see the OMF Endpoint Notes topic.
-
Naming conventions have been changed for some resource types.
- For more information, see the PI Web API OMF Migration topic.
-
Limited migration support has been added for some resource types.
- For more information, see the PI Web API OMF Migration topic.
Fixes and Enhancements:
ContainerNotFoundandStaticInstanceNotFoundevents will now return status code 404 (Not Found), instead of 400 (Bad Request).TypeDoesNotHavePropertyWithSpecifiedIndexhas had its severity downgraded fromErrortoInfo.- The string values
"NaN","Infinity", and"-Infinity"are now accepted for properties of typenumber. - Bug fixes
PI Web API OMF Services 2019
New features:
-
OMF v1.1 data ingress through PI Web API endpoint now supported over HTTPS when OSIsoft Message Format Services are installed
- Support for
createanddeleteactions. updateactions are not implemented.- For more information, see the OMF Endpoint Notes topic.
- Support for