Effect Redline Notice on System Configuration and Upgrades
- November 23, 2025
- 1 reply
- 154 views
Version: Windchill 12.1
Use Case: Versioning Explodes and series alignment is corrupted
Description:
While doing our deployment build we came across this issue. When a Redline Notice is created, this is pushing new version Seeds in this system. e.g 'CHG-AA-1'. This 'CHG-' comes from a preference. the AA-1 is taken up from the version of the Affected Item. This although programmatically created OOTB by Windchill , is directly pushed into the versionida2versioninfo column of the WTPart. The ill effect of this is, when we load our next build we get 'Seed CHG-AA-1' is not available in the HarvardSeries error. We have to put in this seed value as a legacy tag to get around the issue. By continuing to do so, Over the time, the series will explode and get populated with a lot of Junk values just to support Redline.
Q-
1. The best I can do today is get rid of the CHG- prefix, what about the AA-1
how is this handled to make it seamless in the configuration, right now its chaos, every build we will now have to push unnecessary versions in our series?