Question Re: Message Mapping vs Interface Mapping test tabs giving different results. in Technology Q&A

Message Mapping vs Interface Mapping test tabs giving different results.

Former Member — Thu, 23 Sep 2010 21:03:36 GMT

Hi all,

I am developing an interface that always requires an output file to be created (even if there is no data). I have found a way to change my select statement in the JDBC sender to initiate the message even if there isn't any data (using UNION select -1 ID, '' col1, '' col2, etc.) and that seems to work fine. I then put logic in the message mapping to suppress the row that contains the -1 ID value, which would result in an empty file when there is no other data, and should result in a file containing only the correct data when there is data.

So, my problem: I am always getting empty files with this logic. I tested the logic in the message mapping test tab and it worked perfectly, however when I test it using the interface mapping test tab it results in what becomes an empty file!

My source and destination structures are fairly simple:

Root

--row

col1

col2

...

The logic I use to suppress the ID = -1 row is:

=removeContexts([]ifWithoutElse([keepss=true]Not([]equalsS([]ID, Constant([value=-1]))), SplitByValue([type=Each value]row)))

Obviously, I'm stumped - any help would be appreciated!

Edited by: Mike Morrison on Sep 23, 2010 5:04 PM

Re: Message Mapping vs Interface Mapping test tabs giving different results.

Former Member — Fri, 24 Sep 2010 03:32:38 GMT

Hi Mike,

Can you quote the error log..u r getting error in message mappin or interface mapping?

Please suggest the test results for both the mappings.

Thanks,

Sushama

Re: Message Mapping vs Interface Mapping test tabs giving different results.

Former Member — Fri, 24 Sep 2010 11:41:11 GMT

May be you need to re- activate your objects: Service Interfaces, Operation Mapping and re-assign Service Interfaces in Operation Mapping.

Re: Message Mapping vs Interface Mapping test tabs giving different results.

Former Member — Fri, 24 Sep 2010 14:14:29 GMT

Turns out I needed to change the logic for suppressing the row. Although it produced the exact same queue in the message map, using the logic below worked:

=createIf([]Not([]equalsS([]ID, Constant([value=-1]))))