Skip to main content
B
Brn_The_Admin12-Amethyst
12-Amethyst
January 27, 2025
Question

Windchill Versioning and Iteration Changes

  • January 27, 2025
  • 1 reply
  • 425 views

Leadership is wanting to swap from a alphanumerical revisioning system to a purely numerical system. They understand that the changes can not be retroactive to existing components but still want to make the change to future components. Is it possible to setup windchills versioning and iteration system to reflect this desired change? This change would also need to effective for new parts that are created (instead of being A.1 they would be 01.1).

 

Ex:


Part A.1 once revised under the new system would be 02.1 (B.1)


Part C.5 once revised under the new system would be 04.1 (D.1)

1 reply

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
January 28, 2025

Hi @Brn_The_Admin 

Hard work for you. 

It is not possible to mix the versioning schema. 

So you can not have one object with revision from schema A and following revision from schema B

 

It could be done by revision schema set where all letters are included in the configuration but are set that are not useable any more (set legacy to true) and set an Alternate Revision for each letter A-2, B-3, C-4 etc . They can just exist in the system. This way it could work. 

Specifying Alternate Next Revision Labels

 

<?xml version="1.0" encoding="UTF-8"?>
<scheme>
 <series name = "name1">
	 <seed name = "seed_name1">
		<value legacy="true">A<revTo>02</revTo></value>
		<value legacy="true">B<revTo>03</revTo></value>
		<value legacy="true">D<revTo>04</revTo></value>
		<value legacy="true">E<revTo>05</revTo></value>
		<value legacy="true">F<revTo>06</revTo></value>
		<value>01</value>
		<value>02</value>
		<value>03</value>
		<value>04</value>
		<value>05</value>
		<value>06</value>
	 </seed>
 </series>
</scheme>

 

I would say that it is better idea to change the schema with all values on existing data, 

It is not recommended but it is possible to do so without future complications. 

 

PetrH

    Terms & ConditionsCookie settingsAccessibility statement