Additional Parent Node in transformed message

[Jayant Shewale]

Hi

We are facing an issue while transforming a xml
For xml X1 (Attached) When we parse through Transformation T1 we Get output as below , which is not as expected as we get additional parent node as highlighted:
Also attached source and destination messages S1 and D1 for reference

#<[TO<DL_RoadshowObject, @1665408369>(
notes=” “,
classCode=”A”,
expenseCode=”12343″,
endDate=1970-01-01 00:00:00.000000000,
startDate=1970-01-01 00:00:00.000000000,
status=TO<, @216602785>(
value=”CUR”
),
title=”Test-01-Neha”,
dealogicId=33147,
template=TO<, @458225830>(
name=”ECONOMIST_STRATEGIST_MARKETING”
),
securityRule=TO<, @525166668>(
value=”P”
)
), TO<DL_RoadshowObject, @318399906>(
countriesOfOrigin={
TO<DL_CountryOfOrigin, @1965455465>(
country=TO<, @816542101>(
externalValue=”AZ”
)
)
},
classifications={
TO<DL_RoadshowClassificationObject, @1202587177>(
taxonomy=TO<, @1914081922>(
dealogicId=”SEC0011″,
classCode=”S”
)
),
TO<DL_RoadshowClassificationObject, @669830994>(
taxonomy=TO<, @740238584>(
dealogicId=”IND0034″,
classCode=”I”
)
)
}
)]>

Need help confirm the issue with transformation

0

Attachments:

You must be logged in to view attached files.

[Ed Shaw]

Jayant,

It looks like your S1.txt file is actually named DL_EventDownloadParsedResponse_V4.message in your model.  Is that correct?

To reproduce your results here, I will need the files for DL_RoadshowObjectCollection_V4.meta and any other related classes such as DL_RoadshowObject.meta, DL_RoadshowClassificationObject.meta, DL_CountryOfOrigin.meta (probaly most of the DL_* types of classes.

Keeping their original name is important so maybe just put them in a .zip file.  I’m going to upload a test zip with my response, just to be sure just to be sure that .zip is an acceptable upload format.

Thanks,

Ed

0

Attachments:

You must be logged in to view attached files.

[Author]

Posts