Revisiting old thread...again. Is it Groundhogs day?
I would like to know the real deal behind this. PTC is not going to fix this but I can't see why not unless it has something to with WTPartUsageLinks getting all messed up. If to preserve history, I can let that stuff go if it means I can clean up old iterations to remove holds on stuff I want to delete.
The image below shows that MFG view was created off A.7 which means you cannot purge this or anything after that unless you delete A.- (yes, this is how downstream view versions looked back in the day).
Seems like there should be a job or preference to just shift the branch point to the latest iteration A.8. I know there a SQL hacks and I could probably write something to fix it but just really curious about the internal 3rd rail that prevents PTC from fixing this. Why is this a complicated fix?