Announcement

Collapse

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

SQL statement processing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SQL statement processing

    This was uncovered by accident.....

    Mirth variables with an embedded space such as "sending facility". Variable is populated properly and is viewable in mappings tab of the channel messages. When this variable is used in a SQL statement the variable is not passed to the database. Mirth does not flag an error either in execution or in the validate form activity.

    Note I am not a SQL wiz... This may be rudimentary!

  • #2
    Re: SQL statement processing

    Can you paste your SQL statement?

    Thanks!
    -Chris
    Chris Lang

    Comment


    • #3
      Re: SQL statement processing

      INSERT IGNORE INTO ADT (facility, mrn, lname, fname, last_adt_event, last_message_id) VALUES (${sending facility},${mrn},${lname}, ${fname},${adt_event}, ${msg_id} );

      Database is MySQL version 5.0. V

      Comment


      • #4
        Re: SQL statement processing

        Spaces are not allowed in mapping variables. If you are using 1.3.1, the best way to get the sending facility is to use message.source

        Code:
        ${message.source}
        This is available on all messages without any transformation.

        -Chris
        Chris Lang

        Comment

        Working...
        X