Skip to main content
R
RA_91944718-Gravel
8-Gravel
March 18, 2025
Question

Windchill opening old iteration

  • March 18, 2025
  • 1 reply
  • 779 views

I'm having this same problem with Creo 8. Reference topic: https://community.ptc.com/t5/Windchill/Windchill-opening-old-iteration/m-p/693075#M62966 

Opening the assembly I see that there are old iteration of subassemblies. Checking inside the workspace I see the same subassemblies at the latest iteration. How could CREO open an old iteration that is not even in the workspace?

 

If I open the same subassemblies alone they open latest iteration, indicating that the problem is in the assembly. Something is wrong with it and I cannot figure this out.

1 reply

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
March 18, 2025

Create a new workspace and open one of the subassemblies only to see that Creo is actually loading the latest iteration. Save it to your workspace. Open the top assembly and check to see that the latest subassembly is loaded into your assembly. If it isn't, you may have an issue with a corrupt cache. PTC support may be your only option to get this resolved.

R
RA_91944718-GravelAuthor
8-Gravel
March 19, 2025

Sir, I did as you said:
- New workspace
- Open subassembly (confirmed the latest iteration)
- Save
- Open top assembly (the last iteration of subassembly is in the top assembly)


I did this in a new workspace, new cache (deleted .wf), and new windchill user. Tested in a new computer also. Same results.

If I erase de memory of CREO before opening top assembly, it doesn't open the last iteration. 


I'm wondering: Could the issue be in the top assembly? Maybe a corrupt subassembly/part that is not allowing "regeneration"

Could this be only the parameters that are not updating to show the last iteration number, but the model itself is latest. But the parameters of each model comes from the model, not saved inside the topassembly, right?

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
March 19, 2025

When connected to Windchill, all file resolves are handled by Windchill from the database. I just opened an assembly in Notepad and the only reference to the components is the part number (part_number.prt) with no reference to a version or iteration (unless is it in the encrypted data in the file).

When you say 'old iterations', do you mean an actual Windchill iteration or an old part name from save-as or renaming? Windchill will resolve the save-as and rename to bring in the latest component BUT the component internally will carry the original naming until it has been regenerated in Creo and saved.

Terms & ConditionsAccessibility statement