| Author |
Message
|
| Scorpio_16 |
 Posted: Thu May 14, 2009 3:18 am Post subject: MB v6.1 discards the output elements with value 0 |
 |
|
Apprentice
Joined: 15 Dec 2008
Posts: 25
|
Hi
It looks like MB v6.1 discards the output elements with value 0,
which is not the case in v5.0. can anyone let me know what settings do I have to change in the message set to get the output value as 0 if the input value is 0.
Input is xml format and output is Tagged delimited.
Many Thanks |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Thu May 14, 2009 3:25 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Any chance of an example as to whats occurring (ie input mapping to output) it will help me understand the issue if noone else! |
|
| Back to top |
|
|
| Scorpio_16 |
| Posted: Thu May 14, 2009 3:36 am Post subject: |
|
|
Apprentice
Joined: 15 Dec 2008
Posts: 25
|
Input data (xml format)
<SAMPLE_DATA>
<NAME>AAA</NAME>
<ADDR>asdf</ADDR>
<CONTACT>0</CONTACT>
<CHOICE>Y</CHOICE>
</SAMPLE_DATA>
Esql:
-----
SET OutputRoot.MRM.NAME = INputRoot.SAMPLE_DATA.NAME;
---
-
SET OutputRoot.MRM.CONTACT = INputRoot.SAMPLE_DATA.CONTACT;
--
Output Msgset:
----------------
All elements Delimited
Delimiter: |
So the output appears as
AAAA|asdf||Y
If you see the above output the third element is NULL instead of value 0.
this happens in V6.1. (it seems to be working ok in v5.0). How do we avoid this ?
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 14, 2009 3:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What parser is in use for the input message? Have you used a trace to see how the input message is being interpreted?
Would it be possible to substitute
for
to see if this gives better results?
Additionally, how was the message set controlling output produced? Was it migrated from v5 or created under v6.1? If migrated, have you checked to see if all the settings remain as you expect?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu May 14, 2009 4:02 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Also,
is the "CONTACT" field exactly as defined in the output message set (i'm guessing so if it used to work but am checking!). |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 14, 2009 1:46 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
1. Insert a Trace node after the input node and before the output node. Set the pattern to '${Root}' on both
2. Enable user trace and put a message through the flow
3. Examine the trace output carefully
If possible, do this on both v5.0 and v6.1 - that will almost certainly reveal the problem. |
|
| Back to top |
|
|
|
|
