Windchill opening old iteration

[RA_9194471]

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.

[BenLoosli]

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.

[RA_9194471]

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?

[BenLoosli]

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.

[RA_9194471]

By old iterations I mean actual Windchill iterations.

We have a status for each file also, if they are in Project or Production, and this is how I discovered the problem: because I saved the top assembly model tree to excel (1400 individual items) and filtered only by "Project" (resulting in 370 PJ items), so I can see what are the parts that I can modify. But then, when searching that "Project" part in the database I realized the last iteration was not Project, but was already in Production. So in reality only half of 370 PJ items were actually in PJ. Others were just not showing the last iteration.

Example:
In the assembly:

File name - status - Version (Revision.iteration)

Subassembly1.ASM - Project - 2.3

In the workspace (at the same time):

Subassembly1.ASM - Production - 2.4 (Latest)

How could CREO open a file at 2.3 when the 2.4 is in the workspace. And if I open the 2.4 at the worskspace first, and then the top assembly, it stays 2.4. So in the workspace it's all fine!

[avillanueva]

Poking into this. Is this a case of you looking at attributes that are not in sync? Pictures might help but perhaps this is a regenerate issue. Version and iteration should have been updated on download. Things like state can change anytime so must be synced. Note that assemblies do not hold or control what iterations get retrieved. That is the workspace preferences or what you choose on add to workspace. If you choose as-stored, you will get older iterations potentially of dependents. If you select on old iteration of an assembly but leave as latest, you will get iteration you select but the latest of dependents. 

If possible, show screen shots of what you are seeing.