Skip to main content
avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
January 16, 2025
Question

ControlBranch had wrong ViewID for some Parts.

  • January 16, 2025
  • 1 reply
  • 475 views

Noting this for others. I am not sure how to occurred or if there is a WinDU check to spot it. It could have been a bug in older versions that went unnoticed but has since been patch. Some part versions were clearly Design view versions (in the WTPart table) but that same branch shows the right version (VersionID) but the ViewID said it was a Manufacturing view. Clearly a discrepancy. No issues in the display or other actions I could tell. I only noticed it when we did the conversion to Single Level View Versions and got a constraint violation. It was easy enough to correct these and fix the wrong ViewID value. I think I had a total of 200 cases from decades ago. I also tested to see if it was related to using the "reassign view" action. There are cases when users were copying a part from Manufacturing view that it would retain that view when it should have been changed in that save as UI to Design (our process). 

    1 reply

    HelesicPetr
    22-Sapphire II
    HelesicPetr22-Sapphire II
    22-Sapphire II
    January 20, 2025

    Hi @avillanueva 

    You right, one of the case can be the reassigning the view from MFG to design, if the part was in the bom.

    For example,

    You could use save as MFG BOM with some subparts, but this subparts were MFG, but they should have been the design, so you use reassign the view.

    Am I right? 😄

    PetrH 

    PetrH
    avillanueva
    23-Emerald I
    avillanueva23-Emerald IAuthor
    23-Emerald I
    January 20, 2025

    I suspect that was the case but its been so long ago, cannot be 100% sure. Correcting and moving on.

      Terms & ConditionsCookie settingsAccessibility statement