DescribedBy link across different contexts
team:
I want to add DescribedBy documents (not CAD documents) to a part. It needs to automated, preferably by a python script accessing the OData API.
It is possible to add DescribedBy links using
POST Windchill/servlet/odata/v5/ProdMgmt/Parts(id)/DescribedBy
but it requires some WRS configuration as described in this article:
"Follow the steps to implement WTPartDescribeLink creation hooks."
https://www.ptc.com/en/support/article/CS285572
Testing this, I got an error:
"Unable to create entity - Illegal link. \"OEM Part - 4199999-00, Toy Brick, CAG66, B.4 (Design)\" cannot be linked to \"Brick Install Instructions, CAG99, 1.1\" because both objects are not in a PDM context."
After correcting the context, the link could be created fine by WRS/OData. But that's not what we want. We want to keep our contexts as they are, and link across different contexts.
This brings up a question, I am curious. The link can be created manually across different contexts but not when using OData and the REST API. Is this difference in semantics surprising? The page linked below says that this behaviour will not be changed:
https://www.ptc.com/en/support/article/CS175948