Article - CS136867
Renaming an object in Windchill with "publish.republishonepmdocumentchange" set to true causes all previous iterations of object to republish
Modified: 26-Sep-2025
Applies To
- Windchill PDMLink 9.1 to 13.0.2.0
- Windchill Visualization Services (WVS)
Description
- Renaming an object in Windchill with "publish.republishonepmdocumentchange" set to true causes all previous iterations of the object as well as the newly renamed object to republish/publish respectively
- When renaming objects, all of the datasets previous iterations are also published
- How to avoid job submission for all iterations or at least publish the latest iteration during the rename action
- When renaming an EPMDocument with multiple revisions, every version is getting a new representation file, even though the file itself hasn't changed
- Multiple jobs submitted for the same iteration of the object, all being iterations of the same revision
- Is there a setting to prevent representation files from being created unless the primary content file is changed?
This is a printer-friendly version of Article 136867 and may be out of date. For the latest version click CS136867