Some documents visible in the Windchill UI are not returned in the OData API response

[ozclkonur]

Version: Windchill 12.1

Use Case: understand why some documents visible in the Windchill UI are not returned in the OData API response and to identify the required configuration to make both environments consistent.

Description:

Hello,

We are querying part information and associated documents using the same OData request on two different Windchill environments. In our test environment, all documents are returned correctly with the following request:

/Windchill/servlet/odata/ProdMgmt/Parts?$filter=Number eq 'XXXX'& $expand=Versions($filter=State/Value eq 'RELEASED' or State/Value eq 'IMPORTED'; $expand=DescribedBy($expand=DescribedBy($expand=Attachments,Representations)), References($expand=References($expand=Attachments,Representations)), PartDocAssociations($expand=RelatedCADDoc($expand=Attachments,Representations)))

However, in the production environment, some documents that are visible in the Windchill UI under DescribedBy or References do not appear at all in the API response.

• The document is visible in the UI.

• We are logged in with an admin account.

• But the OData API does not return the document.

• This inconsistency only happens in one environment.

We would like to understand:

1. Is it possible for a document to be visible in the UI but completely missing in the OData response?

2. If yes, what could cause this behavior? (TBA, ACL settings, lifecycle states, OData visibility rules, or configuration differences?)

3. What configurations should we check to ensure both environments return the same data?

We kindly request guidance on identifying and resolving this discrepancy between environments.

Thank you.

[Fadel]

Do you see any error in logs ? if you look for the missing documents in DOC domain with their number are you able to see them using REST ?

[ozclkonur]

Here is the issue we discovered:
For example, when I add a DBF document to version A.3, this document is not carried over to the next versions (A.4 or A.5).
Since we always query the latest version, the DBF file added in A.3 does not exist in A.5, so the result appears as null.

In summary, the problem is not the document upload itself; the issue is that documents are not being propagated to the subsequent versions.