Addresses for message don’t match variant

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Addresses for message don’t match variant

  • Creator
    Topic
  • #55162
    Eric Wright
    Participant

      I have a variant that I’ve built, where a segment should be addressed in the 4th group.  But, when I use that variant and read a message into the testing tool (and in production), that segment is being addressed in the 6th group.  In the message I’m using, all of the prior segments are addressed in the 0th group (as expected), and after the last segment of that group there is one carriage return.  Based on that, I don’t know how, with the variant setup, and the message that I’m using, I could have the segment being addressed where it is.

      Here is the message structure:

      MSH

      EVN

      PID

      PV1

      ZCL

      As mentioned, there is one single carriage return after every segment.  Here is the setup for the variant:

      MSH

      EVN

      PID

      [PD1]

      [{ROL}]

      [{NK1}]

      PV1

      [PV2]

      [

      {ROL}

      ]

      [{DB1}]

      [{OBX}]

      [{AL1}]

      [{DG1}]

      [DRG]

      [{

      PR1

      [{ROL}]

      }]

      [{GT1}]

      [{

      IN1

      [IN2]

      [{IN3}]

      [{ROL}]

      }]

      [ZCL]

      The ZCL segment is where I’m having the problem.

    Viewing 2 reply threads
    • Author
      Replies
      • #84388
        Jim Kosloskey
        Participant

          This is thee way I see it by eyeball. I just let the HL/7 or the Xlate tool tell me what the grouping is.

          I also normally use the default message structure and modify it to what I need rather than create a completely restructured variant.

          If you would like to discuss why I do that email me.

          What Version, Message/Event Type message is this anyway?

             Group 0

          MSH

          EVN

          PID

          [PD1]

          [{ROL}]

          [{NK1}]

          PV1

          [PV2]

             Group 1

          [

          {ROL}

          ]

             Group 2

          [{DB1}]

          [{OBX}]

          [{AL1}]

          [{DG1}]

          [DRG]

             Group 3

          [{

          PR1

          [{ROL}]

          }]

             Group 4

          [{GT1}]

             Group 5

          [{

          IN1

          [IN2]

          [{IN3}]

          [{ROL}]

          }]

             Group 6

          [ZCL]

          email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

        • #84389
          Eric Wright
          Participant

            I realized what the problem was, I was looking at the variant for the type of message I was receiving, and comparing it with the translation.  What I hadn’t noticed is, the translation uses a different message type, but the formats are very close to each other.  I’m going to have to separate the translation for this message type from the others so that it’ll address the message correctly.

            Thanks Jim

          • #84390
            Jim Kosloskey
            Participant

              Gets me frequently – the faster I go the more behind I get  ðŸ˜›

              email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.