Article - CS409743
When one creates a new assembly or modify and save an existing assembly, the components on disk appear modified with a current timestamp, even if they have not been modified since Creo Parametric 10.0
Modified: 01-Dec-2025
Applies To
- Creo Parametric 10.0 to 12.4
- Creo+
- Windchill PDMLink 13.1
Description
- When one creates a new assembly or modify and save an existing assembly, the components on disk appear modified with a current timestamp, even if they have not been modified
- Assembly components that have not been modified will receive a new timestamp, even if their file iteration does not change
- In the current folder (local Working Directory) there are tons of parts with a new updated modification date whose contents have not actually been changed
- If there is some re-evaluation of the properties, those impacted files should all iterate, but new assembly with components where there is no change, no iteration, and still the existing iterated file's date has updated, why?
- The end user should be able to filter by date+time which files have been modified in a local storage (off Creo) but cannot
- Why does a new assembly (even from PTC template) once saved, update the component part file's iterations on date and time stamp, even if there is no change, no recalculation and hence no iteration number?
- Make a small change and save assembly makes the iteration of the assembly increasing, not the components, which is as intended, but why does the prt file's date and time update?
- If there is some re-evaluation of the properties, those impacted files should all iterate, but there is no change, no iteration, and still the existing iterated file's date has updated, why?
- The second save does behave as expected but cannot re-set the unintended changes to the stored file's properties
- After upgrading to Creo Parametric 10 seeing large number of unreferenced file that are getting generated
- On Windchill integration environment, there are more cached files showing up in the folder of Windchill vault (such as defaultuploadvault) when checking in an assembly
This is a printer-friendly version of Article 409743 and may be out of date. For the latest version click CS409743