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

Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X

OData custom mapping f. ClassifiedObjects problem

ChrisB
5-Regular Member

OData custom mapping f. ClassifiedObjects problem

Hello,

I created a custom ClassifiedObjects.json configuration for the ClfStructure domain so as to return more properties than the defaults provided by Windchill.

 

REST / OData Version we are using: windchill 2.2.2 REST Services

 

NOTE: we are talking about this type of query, for instance

 

GET [host]/Windchill/servlet/odata/v3/ClfStructure/ClfNodes('CT11101010')/ClassifiedObjects?$count=true

 

All is fine except for the mapping of an internal field whose internal Windchill type is:

 

com.ptc.core.meta.common.FloatingPoint

 

Since we are dealing with a "Real Number" (as stated in the Windchill GUI) I expect this to be mapped as a "Double" or "Single" like so:

 

{
"name":"StockQty",
"internalName":"INVENTORY_ARTICLE_STOCK,
"type":"Double"
},

 

However, using both Double or Single datatypes will yield the following server response:

 

{
"error": {
"code": null,
"message": "The value '(Unassignable)' is not valid for property 'StockQty'."
}
}

 

Mapping the property as a "String" will yield the value "(Unassignable)" in the response.

 

Hence my question: which datatype should be used for mapping FloatingPoint values in OData?

Or is this a bug?

 

Best regards

 

0 REPLIES 0
Announcements


Top Tags