Xlate testing tool error on 5.4.1

[Jenny Young]

Has anyone seen this error before, and can you help me figure out what is wrong?  We have tried using new data, we have tried moving to a new site, we have tried using an Xlate that we know works in the regular flow of data, and each and every time, we get this error.

[0:TEST] QDX_Tcl_SplitList({) failed: unmatched open brace in list

Internal XPM Tcl error

erroCode: NONE

errorInfo:

can’t unset “Hl7FieldsLoaded(2)”: no such element in array

   while executing

“unset Hl7FieldsLoaded($iokey) “

Topic

[Bob Richardson]

Greetings,

I have seen this error in the 5.3 integrator and usually it is the data record.  For ADTs a segment like the NK1 will have a single instance of a double quote which confuses the translation program (xpm) into thinking that there ought to be a list and there is not !!  We must do a couple of things:  complain to the sending application to cleanup their data then resend the offending message and/or scrub the message and resend it – such as using a tcl proc with string map or regsub.

One way to find out what field is the trouble maker would be to clone your xlate; decide on starting at the top or bottom; and begin removing actions until your xlate works.  Tedious but gets to the offending field then you can look at this field in the message and find the ‘bad’ data (again most likely a double quote with no match).

Enjoy.

[John Mercogliano]

One thing that might help narrow down your search.  I have only seen this type of error myself for inline tcl code in a translate, when a tcl command causes an error.  I now only call tcl procs in a translate.  At least now when I get a coding error, the translate tells me the proc that caused it.

John Mercogliano
Sentara Healthcare
Hampton Roads, VA

[Author]

Replies