[Bonnie Giesler]

Just wanted to add a note that this may have have been a java issue because when I opened the detail it was all javascripting errors.  Did not want anyone to think that you could not add fields once you were working in xlate

[Bonnie Giesler]

I never got that far… here is what I did.

1. Selected the 2.2 variant

2. Built the xlate

3. Found that McKesson wanted their charge code in FT1:25 instead of FT1:7 (where everyone else has it).

4. Tried to add 2 user defined fields to the variant.  Got an error saying 24>23.  Tried using existing fields got the same error.

5. Got frustrated and used variant 2.3.1 that has 25 fields in the FT1 and has a DFT^P03.  Recompiled the xlate.  Worked fine

6. Got Jim’s reply.  Tried again using the 2.2 so I could send screen prints and now I can add those 2 fields.

Lessons learned:

1. Post to CloverTech first so I can look stupid but save myself a lot of time.  

2. I will not try to add fields once the xlate has been defined?  I still think it is goofy .

[Bonnie Giesler]

Thanks for the explanation.. it just takes some of us longer.

[Bonnie Giesler]

Never mind.  Got it.

[Bonnie Giesler]

Kind of figured some one would/should indicate the list thing.  I know this is a stupid question (which speaks to my lack of tcl) but what is the purpose of the 0 0 and 0 in this script.  

set xlateOutVals [lreplace $xlateOutVals 0 0 [string is digit [lindex $xlateInVals 0]]

[Bonnie Giesler]

I ended up using this as inline :  xlateOutVals [string is digit $xlateInVals] to a temp field instead of integer -strict.  

When 010001132 was being evaluated with integer -strict it was false and getting a 0 and so the message was processing like a message with this value in PID:3  NCHG-3.

Thanks again for everyone’s help.  Wish I would have asked sooner.

[Bonnie Giesler]

I’ll give string is a try.  

Jim K.

I am just whining-appreciate the forum and all the help!

[Author]

Replies