xltconvert to 5.6

[lisa sater]

Hi,

We were running on 5.51 and have upgraded our development to 5.6.2.  In the 5.6 the implied (0) at the end of each segment ID is appearing.  It was implied in 5.51 so we didn’t see it.

5.51  0(0).MSH.#5.[0]

in

5.62  is is now 0(0).MSH(0).#5(0).[0]

This is making serveral of our Xlates fail to work.  Does anyone have a script that goes and adds the missing (0) to the Xlates?  If so, are you willing to share it?  (Otherwise I know what task I get to add to my list 🙂 )

I figured the xltconvert would have done this.

Thanks!

Lisa

Topic

[Russ Ross]

Thanks for bringing this to the attention of the community.

We potentially could be impacted by this as we have been upgrading to Cloverleaf 5.6.

We have many cases similar to what you described.

I took a look at one of our 5.6 sites I’m currently doing some development on and found several examples of not having the implicit (0) but they seem to be working.

Here are a couple of examples:

0(0).PID(0).#5.[0]

0(0).FT1(%s1).#7.[0]

So I was wondering what specifically you meant by not working so I can see if I can reproduce the same undesired beahaivor to determine the potential impact to our institution.

Russ Ross
RussRoss318@gmail.com

[Tom Rioux]

Lisa,

We are up and running on 5.6.2 here.   We have some older xlates that were converted over that have the older 0(0).MSH.#5.[0] mapping.  We also have some newer ones that use the newer 0(0).MSH(0).#5(0).[0]

mapping.   We also have some xlates that had to have modifications done to them (not due to the upgrade), and use both versions of the mapping.  In all cases, we are not experiencing any problems with the xlates.  

If you could, get us some examples of exactly what “is not working” and maybe we can narrow down your issue.  

Thanks….Tom

[Author]

Replies