Skip to main content
23-Emerald III
February 5, 2025
Solved

Flexible Change Converter issues

  • February 5, 2025
  • 3 replies
  • 1930 views

Version: Windchill 12.1

 

Use Case: Upgrading to 13.0.2 requires change object links be converted to flexible links before UpgradeManager can be run.


Description:

When I run the Flexible Change Converter in report mode, it says I have 164 links to be converted. When I run the convertlinks action, it fails and says that I have an enumerated type of URGENT that is not defined. I have added URGENT to RequestPrioirtyRB, ComplexityRB and IssuePriorityRB and it still fails. I have deleted ALL Change Notices in the system and the report still shows 164 and fails with the error of unable to resolve the URGENT enumerated type.

The change notices were created back in WIndchill 11 or 11.1 days (2017-2018) and have been upgraded since then to 12.0 and now in 12.1. The 12.1 is a test system using the 12.0 production data.

I have had a call open with PTC since early December on this and no resolution from them.

I would think that deleting all of the Change Notices would allow the convert links utility to run.

If anyone has any ideas, please share them as I need to get this system up to 13.0.2.

Best answer by BenLoosli

Ok it is fixed and I now have Flexible links.

Running the converter put the information from the RB.ser files into the Type and Attribute Custom enumerations tab.

Running the convertLinks command, and I now got a missing TRIVIAL enumeration.

Added this through the Windchill UI and run convertLinks and get a missing ROUTINE enumeration.

Added it and run convertLinks again and it goes through.

Then I run the convertEligibleObjects command and finally the setFlexible command.

My report now shows my links as being Flexible so I can go back to my production system and repeat this and then do the 13.0.2 upgrade.

 

Thanks for pointing me in the right direction.

PTC Tech Support has had this call for 2 months and never asked about running the converter.

3 replies

BenLoosli23-Emerald IIIAuthor
23-Emerald III
February 5, 2025

The URGENT enumarated va;lue was added with the enumcustomize utility into the respective RB.ser files and then the ant -f MakeJar.xml custUpdate was run on the system and then method servers restarted.

Is adding enumerated items through the UI the 'new' preferred method for adding them?

20-Turquoise
February 5, 2025

Adding thru the UI was added in 12.1.1.0:

https://support.ptc.com/help/wnc/r12.1.1.0/en/?_gl=1*14kx08i*_gcl_au*MTg3Mjc5ODk4OC4xNzM4MTY0MjA5LjE2NDYzNTUzMzcuMTczODc4NzQwMC4xNzM4Nzg3NDA1*_ga*MTI0ODMzNzM5NC4xNzIyMzUwMjA5*_ga_7NMP2MSYPM*MTczODc4NzM5My4zNzUuMS4xNzM4NzkxODI5LjMuMC4w*_ga_CBN5QVB9VJ*MTczODc5MTQ4My42MjMuMS4xNzM4NzkxODI4LjAuMC4w#page/Windchill_Help_Center/NewandChanged/NewandChanged_12_1_10_MappingAdmin_ModEnum.html#

 

This is a much better way. Only drawback so far is you can't tell what are ootb entries and what are the custom ones you have put in place. Somebody actually posted something on this.

My impression was until you ran this utility the system would still look at the legacy rb files however in your case the flexible change converter maybe only looking at the new way?

avillanueva
23-Emerald I
23-Emerald I
February 5, 2025

I remember running this back in 2022 when we were on 11.1 and moving to 12.0. We ran in then. Had you run it then to convert the old data or is this your first time converting your system?

BenLoosli23-Emerald IIIAuthor
23-Emerald III
February 5, 2025

First time doing a conversion to flexible links.

BenLoosli23-Emerald IIIAuthorAnswer
23-Emerald III
February 5, 2025

Ok it is fixed and I now have Flexible links.

Running the converter put the information from the RB.ser files into the Type and Attribute Custom enumerations tab.

Running the convertLinks command, and I now got a missing TRIVIAL enumeration.

Added this through the Windchill UI and run convertLinks and get a missing ROUTINE enumeration.

Added it and run convertLinks again and it goes through.

Then I run the convertEligibleObjects command and finally the setFlexible command.

My report now shows my links as being Flexible so I can go back to my production system and repeat this and then do the 13.0.2 upgrade.

 

Thanks for pointing me in the right direction.

PTC Tech Support has had this call for 2 months and never asked about running the converter.

22-Sapphire I
July 31, 2025

I created this instruction within an overall upgrade procedure document for this step. May be helpful for others. Note:This was from a two step upgrade, 11>12>13.

 

Run commands per CS262354

Note: If not done, fails at Update Container Templates.

 

Have to do this for each rehearsal upgrade and for the production upgrade.  Result is stored in the 12 database and has to be brought over to 13.

 

Windchill has to be running for these commands.

 

QUERY CURRENT CONDITION

java wt.change2.flexible.FlexibleChangeConverter -action report

examine report content

 

MAKE CHANGES

java wt.change2.flexible.FlexibleChangeConverter -action convertLinks

 

java wt.change2.flexible.FlexibleChangeConverter -action convertEligibleObjects

 

java wt.change2.flexible.FlexibleChangeConverter -action setFlexible

 

QUERY CURRENT CONDITION - CONFIRM

java wt.change2.flexible.FlexibleChangeConverter -action report

examine report content

 

Has to say Flexible in the output file created in /Windchill/temp

MikeLockwood_0-1753977811976.png

 

 

Backup db > .BAK file, copy to DB server for 13