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

e4x for each notation

  • Filter
  • Time
  • Show
Clear All
new posts

  • e4x for each notation

    I've googled around a little bit and I tried following the faqts link in some of the forum posts but it is down. I'm wondering if anyone knows the trick for doing for each syntax when there is a dot in the name of the tag one is looking for such as:

    for each (x in msg..ORU_R01.PATIENT_RESULT) - i've tried quotes, curlies etc. any ideas or a website? at this point I am planning on using a for loop and finding the length, but I was just if anyone knew.


  • #2
    Re:e4x for each notation


    for each (x in msg..[ORU_R01.PATIENT_RESULT])

    Not sure if that will work at all...but it's worth a try. E4X is tricky like that and there is really no documentation.
    Chris Lang


    • #3
      Re:e4x for each notation


      Thx for the suggestion - no dice, the validator doesn't like it...unless an e4x ninja is hiding out there, i think i'm using the loop and moving on


      • #4
        Re:e4x for each notation

        Perhaps the next syntax works

        for each (x in msg..['ORU_R01.PATIENT_RESULT'])


        • #5
          Re:e4x for each notation

          unfortunately seems like the dot operator needs escaped - I've got nothin


          • #6
            Re:e4x for each notation

            stumbled across this: - looks like a great e4x doc, also the syntax for the dot operator:

            x in msg..*["ORU_R01.ORDER_OBSERVATION"]