Hi Arnab,
Apologies, didn't notice the row part - I was just examining the actual fields being converted.
Yes, if it is converting as row instead of Details, then it would cause the mapping error.
The MTB module is not a 1-1 match with the FCC logic in a File adapter, so there are differing behaviors. But I am not sure if the generation of the row node is a default behavior of the MTB module.
Can you try removing the "ignorerecordsetName" parameter and see if the conversion is still <row> or not?
If all else fails, I would suggest that you change the Data Type (rename Details to row) and update the message mapping accordingly.
Rgds
Eng Swee