ExcelTransformBean and PayloadSwapBean working in Tandem

[Former Member]

Hi , I have a interface Sender mail adapter containing .xslx file in attachment.I need to convert the .xslx file to XML and then use it. I am using the module in the below sequence..as in the screenshot. For the PayloadSwapBean the params are: swap.keyName    =Payload-Name swap.keyValue1  =MailAttachment-1 ModuleSequence.JPG But the problem I am getting is the payload still is in .xslx format. This is why the mapping is failing. But astonisingly if I dowload the MailAttachment-1.xslx file and see that,it opens in notepad++, and that is the converted xml. So the TransformationBean works but my purpose is not solved. Payload.JPG

[engswee]

Hi Abhishek

You did not provide the audit/message log showing what is happening during runtime.

Also please provide screenshot of the following tabs for the message:-

• Message Attributes
• Attachments

I will need all this in order to analyse this issue further.

Regards

Eng Swee

[Former Member]

Hi Eng,

Here are the Mesage Attribute/Attachment screenshots

I am being confused coz when I use AF_Module/MessageTransformBean, it converts the attached csv in mail to xml and I see that in payload.But here I dont see the payload and while clicking download it says its MailAttachment.xslx . It needed to be MailAttachment.xml.

[engswee]

Hi Abhishek

I'm asking for the third time for a screenshot of the audit/message log. Without this, it is a bit hard to imagine what happened during runtime processing in the channel.

From the incomplete information that you have provided, I can roughly guess that the swap and Excel conversion was completed successfully. Note that the Excel converter converts the content of the payload/attachment but does not change the filename. As such, that's the reason why it still prompts you to download as .xslx although the actual content is in XML when viewed in a text editor. Changing the filename is a different issue altogether since it does not affect processing in PI.

Your main issue seems to be caused by mapping failure. My suggestion is you take the downloaded XML content and test it out in ESR message mapping test functionality. The mapping may fail due to a lot of different reasons, but my first guess would be a mismatch between the converted XML versus the defined DT/MT used in the mapping. Check for typo errors or differences in namespace.

Regards

Eng Swee