Mirth Connect 4.1.0 Released!

Mirth Connect 4.1.0 is now available as an appliance update and on our GitHub page. Mirth Connect 4.1.0 includes new features such as new event log messages, additional fields to the Welcome to Mirth Connect screen, new information included in alerts as well as many smaller changes, updates, and improvements. This release also contains several improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

please make the xml stay in incoming msg

  • Filter
  • Time
  • Show
Clear All
new posts

  • please make the xml stay in incoming msg

    I would like to know how to why my xml on the incoming message always return to empty tags like this:

    <?xml version="1.0" encoding="UTF-8"?>

    Do I really need to paste each time??

    <?xml version="1.0" encoding="UTF-8"?>

    thanks guys!

  • #2
    Release make the xml stay in incoming msg

    Change your select statement to not do SELECT * but the actual fields. If you don't change the select statement though, Mirth shouldn't over-write the XML that is there.
    Chris Lang


    • #3
      Release make the xml stay in incoming msg

      HI Chris!
      The actual fields are real many, and they are from various tables here without realtionships because I am working on a turnover system. Anyway, thanks for clearing it out to me!
      BY the way, union doesn't work here right? There is no other way for me to select all the required fields to populate my hl7 because inner join only works for referenced tables.