cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X

Translate the entire conversation x

Windchill REST Services endpoint to create a PartUsageLink is missing

CB_12625553
12-Amethyst

Windchill REST Services endpoint to create a PartUsageLink is missing

Version: Windchill 12.1

 

Use Case: I am attempting to create a PartUsageLink using Windchill REST services: URL: POST /ProdMgmt/Parts('{PartId}')/Uses


Description:

A Vanilla build of Windchill allows me to create a PartUsageLink using this REST endpoint. However, when we deploy our Implementation Partner's CCD build to our environment, that endpoint is no longer available. They are not sure why this is. There are no customizations or configurations done to any REST endpoints directly. What would cause this problem and how can I make this endpoint available again?

 

Below is a pic showing the REST endpoint available in our DEV environment (Vanilla) vs. our INT environment (with configurations deployed).

 

CB_12625553_0-1747679268025.png

 

When I attempt to hit the endpoint in INT I get this response:

 

{
    "error": {
        "code": "OPERATION_NOT_SUPPORTED",
        "message": "The operation is not supported"
    }
}

 

 

The POST /ProdMgmt/Parts('{PartId}')/PTC.ProdMgmt.CreateUses returns the same error. Thank you for any help or suggestions!

ACCEPTED SOLUTION

Accepted Solutions

Part Usage Instantiable attribute was set to No. When toggling back to Yes it showed up. The reason it was set to No was because we were trying to Sub-type the Part Usage link, but then PTC recommended that we do not Sub-type that class. In removing the Sub-type we forgot to toggle back. We updated our CCD build to leave it as Yes.

 

CB_12625553_0-1747944594407.png

 

View solution in original post

2 REPLIES 2
Fadel
22-Sapphire III
(To:CB_12625553)

I'm handling the related TS case 

Fede

Part Usage Instantiable attribute was set to No. When toggling back to Yes it showed up. The reason it was set to No was because we were trying to Sub-type the Part Usage link, but then PTC recommended that we do not Sub-type that class. In removing the Sub-type we forgot to toggle back. We updated our CCD build to leave it as Yes.

 

CB_12625553_0-1747944594407.png

 

Announcements
Top Tags