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

Enabling ODATA API/navigation to fetch connected reference document based on navigation criteria

Enabling ODATA API/navigation to fetch connected reference document based on navigation criteria

Currently Windchill ODATA  API (GetPartStructure) is available to fetch parts from structure based on navigation criteria. Also navigations are available to get connected CAD or described by document. In case of reference document (floated document) , we have navigation which return latest version of reference document. Filtering based in navigation criteria has not been implemented yet. It would be helpful if we can filter floated documents along with parts as well

4 Comments
olivierlp
Community Manager
Status changed to: Clarification Needed

Thank you for publishing your idea. We need more information as specified in the form you saw in the submission process. (Questions below). The more details and context you give, the better.
Please let us know within the next two weeks.

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
2. What product & version are you currently running?
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
4. What is the use case for your organization?
5. What business value would your suggestion represent for your organization?

SD_8997381
3-Visitor

Hello Team,

Thank you for reaching us out.

This is regarding one of the ongoing implementations at IKEA where I am part of solutioning team for a Windchill application and responsible for working on solution design based on business need.

Currently, we have Windchill 12.0.2 version on production environment and we are working on enabling ThingWorx Application to access Windchill data for third party / non-IKEA Users. The intend of this application is user should be able to access only shared data in specific format . The control on data exposed to users and way of showing or arranging data as per user convenience is more feasible.

ThingWorx UI is populated with required information using Windchill ODATA APIs in backend. As a Part of a need, we are working on enabling windchill part structure based on certain navigation criteria. Windchill OOTB ODATA API PTC.ProdMgmt.GetPartStructure from prodMgmt/v5 version retrieves part structure based on navigation criteria. But it only returns parts. We also have the OOTB navigations (References, DescribedBy, PartDocAssociations) to get connected WTDocuments and CAD objects. But in this scenario, documents are fetched with latest config spec and way to filer based on navigation criteria is not enabled.

Hence , we are facing challenge , in case of Reference document where document can float in structure for a part version and filtering right version becomes challenging using OOTB approach

 

Let me know if anything else is needed

 

Thank you,

Dipshree Shinde

 

olivierlp
Community Manager

Hello, 

Thank you for your idea and the information provided.

olivierlp
Community Manager
Status changed to: Acknowledged