Posted: Wed Apr 28, 2004 2:55 am Post subject: Migration issues from V2.1 to V5
Acolyte
Joined: 23 Jan 2002 Posts: 72
Can some confirm or enlighten me accordingly please
I have migrated message sets from 2.1 to V5 and followed all the rules and options regarding whether the elements from 2.1 are to be global or local etc....but in my 2.1 sets I have a bunch of valid values which were used to set a fixed length string from As400 input i.e field "fred" has a minimum value length of 7 and is string and therefore equates to a fixed length of 7 alphanumeric, but on migrating, the element has been created as expected but no valid values have been migrated and I was expecting them to be migrated as attributes of the element in the XML schema way of doing things in V5 although i am not sure if i read correctly that they would be migrated at all (confirmation would be helpful). On saving the migrated set I get warning errors saying that the elements have a zero value like it is expecting some attributes to be attached, and you can attach manually to sort it but was expecting not to have to key hundreds of these things in. any help appreciated. the formats for these MRM are all CWF by the way.
FYI (although it may be too late for GYR now !)
Element Values are migrated from 2.1 to V5.
They appear as value constraints on the simple type of the migrated element.
For Example :
Quote:
If you have and element of type string with an attached max length element value of 7 in V2.1
In V5 you will have the same element which will have a new local type which is a restriction of xsd:string. This new local type (called "xsdstring -") will have a "Value constraints" section in it's properties an here can be found the max length setting of 7.
The warning that GYR is refering to relates to something completey different.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum