Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many 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

Data Type mismatch

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

  • Data Type mismatch

    In 1.7, changing the Incoming Data Type of a Channel does not update the Data Type in the message template of the Destination. The only way I've found around this is to re-create the Channel.

    Can anyone else confirm this issue so I know its not just my machine config?

  • #2
    Reata Type mismatch

    Change the outgoing data type of the source transformer. You can change the incoming and outgoing data types of both the source and destination transformers. These are all done separately to allow in-channel protocol changing.
    Jacob Brauer
    Director, Software Development
    NextGen Healthcare

    sigpic

    Comment


    • #3
      Reata Type mismatch

      Ahh, works wonderfully. Thanks!

      Comment


      • #4
        Reata Type mismatch

        Ahh, works wonderfully. Thanks!

        Comment

        Working...
        X