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

Windchill REST Services 1.5 - $levels working?

Regular Member

Windchill REST Services 1.5 - $levels working?

Hi everyone,


I was playing around with WRS 1.5 with the help of "Windchill REST Services User’s Guide 1.5", using SoapUI and a Windchill 11.1 M020 CPS05 instance.


I am aware that GetBOM might be deprecated in future, however my question might be relevant also for other REST methods.

On page 166 there is written the following:

Reading the Bill of Material (BOM)
This example shows you how to read the bill of material (BOM) for a product
structure. Use the following POST URI with the request body.
POST /Windchill/servlet/odata/ProdMgmt/Parts('OR:wt.part.WTPart:44148884')/
PartUse,Occurrences;$levels=max) HTTP/1.1
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body

I used that example, without giving a NavigationCriteria (thus the Request Body was {}.

However I found out that when I have "$levels=max" in, I always get

{"error": {
   "code": null,
   "message": "The URI is malformed."

as a response. Even when replacing max by 1 or 2. When I take it out, everything works fine with all levels.

Question: is that a known behaivour? If so, what should be used instead of $levels?


Thank you in advance,


LiveWorx Call For Papers Happening Now!