- This topic has 5 replies, 3 voices, and was last updated 14 years, 5 months ago by
.
-
Topic
-
-
Replies
-
-
Does your Xlate reference a variant? If so you need to make sur that variant was migrated to the new environment.
Orm is not a standard message type as far as I know and so either you have a variant defined which does not now exist (Clovelreaf defaults to the standard if there is no variant) or someone modified the standard definition distributed with Cloverleaf in your prior release (not something I would recommend). When you upgrade, the standard distributed HL/7 definitions get replaced with the new versions so if someone modified the prior release standard definition, the modification is gone.
email: jim.kosloskey@jim-kosloskey.com
-
Yes….the xlate references a variant. Within the variant they created Orm instead of changing ORM. Within a variant, if you want to change an order format should you change ORM instead of creating a new message? Maybe I should try to find the changes, delete Orm and put them in ORM. They also have fields in the variant like Pv1 instead of PV1. Should changes have been made in the PV1 field and saved?
Your help is greatly appreciated…tria
-
My xlate is reading the correct format now. I deleted Orm in the variant…and changed ORM to the correct format. The xlate still didn’t see the correct format until I copied the Orm file under messages back in and renamed it to ORM (from a backup). Now everything seems fine. There’s probably a better way to fix this, but at least it’s working again.
-
-
I have to correct my previous response. My changes created other problems on other xlates. So I called support to get help. They figured out what I need to do. Since I cannot reconfigure the xlate format using Orm, I have to save it with ORM and then go into the xlate file itself and change the name to Orm and save it using wordpad. I haven’t tried it yet, but it looks promising.
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
