Hello,
I opened the messageSet.mset using the message set editor. If you click on the Text_CSV then look under the Data Element separation settings it suggests the delimiter is a comma. But when I run the flow in debug mode it does not pick up the Elements (Eid, Esal & Ecountry). I sent this message to the flow Name,123,54000,UK.
Eventually I found the correct format of CSV file that fits the message definition. But only after I opened the message definition CSV_mdef.mxsd in text editor. Then I could see this line:
<tdsStructRep delimiter="@" messageSetDefaultRep="Text_CSV"/>
I think it is funny that when I open the message definition CSV_mdef.mxsd using the Message Definition Editor GUI the @ delimiter is nowhere to be seen.
Now I am sending Amit@123@54000@UK
Which produces:
<Emp><Ename>Amit</Ename><Eid>123</Eid><Esclor>54000</Esclor><Ecountry>UK
This is what I expected.
Do you think this is the best way to determine the correct input message?
Amit
------------------------------
Amit Kapila
Integration Developer
eComm Europe Limited
London
UK
amitkapila@hotmail.com+44 (0)2085707240
+44 (0)7976529902
------------------------------
Original Message:
Sent: Sat March 13, 2021 10:05 AM
From: Amit Kapila
Subject: Reverse construct input CSV
Hello,
I have a message set within which there is a message definition. However an example of the what the CSV looks like cannot be found. I have sent several CSV files through the message flow but the elements aren't all being picked up under the message assembly.
Is there a way to derive from the definition what the format of the CSV should be?
There is an mxsd file which I attach to this message. What else should I look for?
Amit
------------------------------
Amit Kapila
Integration Developer
eComm Europe Limited
London
UK
amitkapila@hotmail.com
+44 (0)2085707240
+44 (0)7976529902
------------------------------