xlateStrSubstring error

This topic has 2 replies, 2 voices, and was last updated 4 years, 7 months ago by Jim Kosloskey.

Creator

Topic
February 24, 2020 at 1:44 pm #115691

Rich
Participant

Team,

I’m trying to pull the first three numbers from PV1.18 (Patient ID) for comparison and possible supression.

I did the following:

xlateStrSubstring 0 2

and am getting the following error in the testing tool:

MESSAGE 1
Tcl callout error
xlateStrSubstring 0 3:

errorCode: NONE

errorInfo:
bad type “nm”: must be c, d, v, or x
while executing
“xpmstore $xlateId $outAdd $outType [string range $inValue $_first $_last]”
(procedure “xlateStrSubstring” line 15)
invoked from within
“xlateStrSubstring 0 3”
<End of errorInfo>

Why??
Creator

Topic

Viewing 0 reply threads

Author

Replies
- February 24, 2020 at 5:09 pm #115711
  
  Jim Kosloskey
  Participant
  
  What is the Destination of the STRING Action?
  
  Also it is curious the error trace shows 0 and 3 rather than 0 and 2.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
  - February 26, 2020 at 10:44 am #115756
    
    Jim Kosloskey
    Participant
    
    It is the map Function of the STRING Action. I forgot to include that. you will also need to escape the escape character \\.br\\
    
    email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
Author

Replies

Viewing 0 reply threads

You must be logged in to reply to this topic.