cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

FileBased Revision

Highlighted
Newbie

FileBased Revision

We have legacy data with single digit version '0' and double digit version '00' which needs to be loaded through loaders. We are using filebased series for this with the below entries.

<value>00</value>

<value>0</value>

<value>01</value>

<value>1</value>

<value>02</value>

<value>2</value>

<value>03</value>

<value>3</value>

<value>04</value>

<value>4</value>

<value>05</value>

<value>5</value>

<value>06</value>

<value>6</value>

<value>07</value>

<value>7</value>

<value>08</value>

<value>8</value>

<value>09</value>

<value>9</value>

The load is success for the parts having versions "0" as well as for "00". But for the rest it is working only for double digit version like '01','02','03',.... and getting the error message for single digit version as "Cannot create series sort value -" because its identity is not unique. Windchill version is 10.2.

Tags (3)
3 REPLIES 3

Re: FileBased Revision

Any solution for this issue? Or any other approach?

Re: FileBased Revision

Try to delcare them also as legacy:

<series name="alpha">

<value legacy="true">-</value>

<value legacy="true">a</value>

<value legacy="true">b</value>

<value>A</value>

<value>B</value>

</series>

You will be able to load objects with the values -, a, b but you won't be able to create new ones over the GUI.

Re: FileBased Revision

If declaring as legacy doesn't help it would be helpful to know if data existed in the system that used this versioning scheme prior to it being updated. It could be that the seriessortvalues are all out of whack or something along those lines. If that's the case a tech support case may be the way to go here.