After saving an imported assembly: multiple parts no longer in correct locations!
I'm using Creo Parametric 8.0 and one of our vendors uses Creo Elements/Direct: they typically send me both .stp and .pkg assembly files and I'm running into this issue regardless of what format I import their assembly from.
Initially the import process works very well; I have a lot of success importing and opening these CAD assemblies without too many errors. I will then save a backup of these assemblies (save as-> save a backup) either locally or to our companies cloud servers. Naturally I save it in Creo 8's native format (.prt and .asm files) so I don't have to go through the process of re-importing.
This is where the problem arises: after closing the assembly, rebooting CAD or my computer, etc. and then I go back and re-open that assembly I will open the top-level .asm file and run into a ton of parts that have completely lost all of their orientation/position information inside the assembly. I'll have hundreds of tiny PCA components floating out in space as well as larger plastic panel parts dislodged and oriented like crazy. Some parts stay where they should. I've noticed that if I delete the entire backup library, re-import, and save another backup that I'll run into different parts that move to different positions. Also occasionally this doesn't happen at all and the file seems to save and re-open without any orientation losses. There seems to be no method to this madness and it is extremely frustrating.
I've noticed Creo generates coordinate systems for every part it imports inside these assemblies and I don't modify or delete those at all. I've had this happen immediately after assemblies that have been saved without doing any sort of modifications after the initial import.
Questions:
1. Is there a set of actions I'm not taking in order to "lock-in" the part orientations once I've successfully imported?
2. Is this some sort of bug I'm encountering? Obviously my first assumption is I'm doing something wrong in my workflow but if that's not the case what should I be doing to report this bug?

