Working with the msg object in external library about connect HOT 2 OPEN

UPDATE:
I'm trying to move this very functionality inside Mirth and still have issues with this. I don't know if this is a bug or not. I'm trying to reach a field within a segment logger.debug(msg['PID']['PID.4']['PID.4.1'].name()); and I get back TypeError: name is not a function, it is xml.. In the Message Trees I see that the node is there with an [empty] value. I tried to do the same thing with a different field and I do get the node name, for instance logger.debug(msg['PID']['PID.5']['PID.5.3'].name()); which its value also [empty] but I get back PID.5.3.

Why the inconsistency?

from connect.

Your actual inbound message probably does not have a PID.4.1 node.

The outbound template in your transformer, if present, gets serialized to the tmp variable.

The inbound template is only there for drag-and-drop purposes. msg will be the contents of your message, which doesn't necessarily look anything like your inbound template that you view in the Message Trees tab.

To your original question, if you are trying to stringify the XML for a node, use msg['PID']['PID.4']['PID.4.1'].toXMLString(). That will return an empty string if the node doesn't exist instead of throwing an exception and include the element name even if the node only contains text children.

from connect.