cancel
Showing results for 
Search instead for 
Did you mean: 
Security Alert Log4j Security Vulnerability. Click here to know more.
cancel
Showing results for 
Search instead for 
Did you mean: 

Switch Version Series of existing objects?

sdrzewiczewski
5-Regular Member

Switch Version Series of existing objects?

We've got some legacy data that uses an old versioning series. Is it possible to change the versioning series that an object uses? I'm assuming that some java/jsp/something along those lines would be needed.

I thought I saw a post on here, but was unable to find it searching...

Thx,
Steve D

4 REPLIES 4

Has anybody been able to switch the versioning series an object uses after it's been created?

From a windchill shell try executing java wt.vc.MasteredSeriesCleanser
This class can update the revision series for an object type based on the OIR.

The usage page displays all of the options and shows examples.


Todd Votapka
BAE Systems IT

Just tried this... Not so good. What I have is parts that are using
MilSpec and the context is using StateBased. I ran the utility it had
4500 object that I identified, I copied down some of the number to
validate that it did or didn't work. After it appeared to complete
successfully I was not able to Revise any of the objects that I had
listed. One of them actually gives me an error when I try to search for
it ".wt.series.seriesResource... wt.series.SeriesException. The revision
value is not valid within the series. .. series.StateBased..Nested
exception is. wt.series.SeriesException. The revision value is not valid
within the series. .. series.StateBased



Looks like I'll be restoring my test system.






Thanks for the replies. Tech support actually came through and it was a very easy fix.

So my main issue was the original versioning series was MilSpec which goes -, A, B, C etc... The new series was StateBased which goes 1,2,3,4...,A,B,C

So there is never a - in the new series. The solution was to export the filebased versioning series, modify the Numeric Seed and put a - before the 1. Upload the series and restart. All the errors went away, I was able to Revise, Reassign Lifecycle and find the objects in search results.

Now my issue is all parts start with a - and we want them to start with the 1, so i'm about to edit the filebased series again and put the legacy="true" on the - element. So it's a valid legacy version, but new objects won't use it.

Announcements