1. Home
  2. Support
Article - CS336378

Is versioning of ODATA API must be used for each customization done?

Modified: 04-Jan-2021   


Applies To

  • Windchill Navigate (formerly ThingWorx Navigate) 8.5.3 to 9.1

Description

  • Is versioning of ODATA API must be used for each customization done?
  • Example of change between versions of ODATA API breaking customization :
Starting ProdMgmt/Parts v5, 'PartAssociations' is not existing anymore and it has been replaced by PartDocAssociations.

When calling Windchill/servlet/odata/v4/ProdMgmt/Parts('VR:wt.part.WTPart:87539') you can see :
<a:link rel="http://docs.oasis-open.org/odata/ns/related/PartAssociations" type="application/atom+xml;type=feed" title="PartAssociations" href="https://XXXXX.ptcnet.ptc.com/Windchill/servlet/odata/v4/ProdMgmt/Parts('OR:wt.part.WTPart:438037')/PartAssociations"/>

And when calling Windchill/servlet/odata/ProdMgmt/Parts('VR:wt.part.WTPart:87539') it doesn’t exist anymore but there is :

<a:link rel="http://docs.oasis-open.org/odata/ns/related/PartDocAssociations" type="application/atom+xml;type=feed" title="PartDocAssociations" href="https://XXXXX.ptcnet.ptc.com/Windchill/servlet/odata/v5/ProdMgmt/Parts('OR:wt.part.WTPart:438037')/PartDocAssociations"/>

 
This is a printer-friendly version of Article 336378 and may be out of date. For the latest version click CS336378