Skip to main content
O
ozclkonur14-Alexandrite
14-Alexandrite
August 20, 2024
Solved

Version Information Discrepancy in SQL Query for CAD Drawings

  • August 20, 2024
  • 1 reply
  • 871 views

I'm encountering an issue with a CAD drawing part where the version is labeled as B2. The problem arises in the `epmDocument` table where the `[versionLevelA2versionInfo]` value is consistently showing as 1. Despite there being 6 versions (A 1, A 2, A 3, A 4, B 1, B 2), all records display the value as 1. This issue persists across all data entries, although the versions appear correctly in Windchill.

What could be causing this discrepancy, and how can I resolve it? Additionally, is there another method to check the versions of these parts via SQL? Note that the same issue is observed in the `wtpart` table as well.

Best answer by avillanueva

That column will always show 1 in your case. If you are using view versions (Design, Manufacturing) which only applies for WTPart, then that column will move based on the view version level.. Design view and all epmdocuments will always have a 1.  if you create a manufacturing view version on a WTPart, it will be a 2. 

I think what you need to be looking for is ITERATIONIDA2ITERATIONINFO. There you will see unique numbers for each check in or iteration. Your image shows multiple iterations for revision A and B. 

1 reply

avillanueva
23-Emerald I
avillanueva23-Emerald IAnswer
23-Emerald I
August 20, 2024

That column will always show 1 in your case. If you are using view versions (Design, Manufacturing) which only applies for WTPart, then that column will move based on the view version level.. Design view and all epmdocuments will always have a 1.  if you create a manufacturing view version on a WTPart, it will be a 2. 

I think what you need to be looking for is ITERATIONIDA2ITERATIONINFO. There you will see unique numbers for each check in or iteration. Your image shows multiple iterations for revision A and B. 

    Terms & ConditionsCookie settingsAccessibility statement