cancel
Showing results for 
Search instead for 
Did you mean: 

XML attributes wrong order in mapping

Former Member
0 Kudos

In XI SP16

I am building a mapping based on a dataype using XML attibutes.

The datatype looks like:

Test_Node ComplexType

a attribute xsd:string

<b> b</b> attribute xsd:string

c attribute xsd:string

d attribute xsd:string

e attribute xsd:string

I use this data type in the message type (this is correct).

When I load it into the mapping I can see the following thing:

Test_Node ComplexType

a attribute xsd:string

c attribute xsd:string

d attribute xsd:string

e attribute xsd:string

<b> b</b> attribute xsd:string

The second attribute goes to the last position. As I use this to build a flat file I don't get the expected flat file.

This is a consistent behaviour with all similar mapping.

I tried to put the last attribute in second position but I think this is not the way to do it (if this is fixed in the future that can cause problems).

Any suggestion is welcome.

Thanks.

Gabriel

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This seems to be a very strange problem. Since you are saying this behaviour is consistent, suggest to raise a OSS Notes.

Regards,

Jai Shankar.

Former Member
0 Kudos

Hi ,

Strange error. But can you try refreshing the cache. helps most of the time if you have created the DT and then changed it.

Also, if thats not the case , try creating another DT and see if u get the same error.

Regards

Vijaya

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

You are right even i am facing the same problem.

Regards,

Sudheer.

former_member206604
Active Contributor
0 Kudos

Hi,

Yes this is kind of a strange error even I faced it when I am doing a External Definition with the attributes xmlns and targetNamespace. Also with some of the attributes so I just changed the name of the attribute with sequence numbers.

Regards,

Prakash

Former Member
0 Kudos

Hi,

Just some quick ideas :

-Is the latest version of your datatype, message type active ?

-Are you sure you are using that message type in the mapping ? ( check namespaces in case similar message types exist )

-Did you try to create once from scratch again to see if it's always the smae behaviour ?

rgds dirk