xlateStrReplace 0 1 error

Clovertech Forums Cloverleaf xlateStrReplace 0 1 error

  • Creator
    Topic
  • #116688
    Stewart
    Participant

      Getting the following error when using STRING XLT xlateStrReplace.  Any suggestions?

      MESSAGE 1
      Tcl callout error
      xlateStrReplace 0 1:

      errorCode: NONE

      errorInfo:
      bad type “st”: must be c, d, v, or x
      while executing
      “xpmstore $xlateId $outAdd $outType [string replace $inValue $_first $_last $_newStr]”
      (procedure “xlateStrReplace” line 24)
      invoked from within
      “xlateStrReplace 0 1”
      <End of errorInfo>

    Viewing 3 reply threads
    • Author
      Replies
      • #116689
        Jim Kosloskey
        Participant

          Did you provide a new string? It looks like all you provided was the _first and _last.

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

        • #116690
          Stewart
          Participant

            Same when this is included.

            MESSAGE 1
            Tcl callout error
            xlateStrReplace 0 1 A:

            errorCode: NONE

            errorInfo:
            bad type “st”: must be c, d, v, or x
            while executing
            “xpmstore $xlateId $outAdd $outType [string replace $inValue $_first $_last $_newStr]”
            (procedure “xlateStrReplace” line 24)
            invoked from within
            “xlateStrReplace 0 1 A”
            <End of errorInfo>

          • #116696
            Stewart
            Participant

              I saw where this had been posted a couple of times when I searched and it wasn’t answered in any of the threads.  I tested in 6.1, 6.2 and 19.1.2 and only saw this error in 6.1.  In order to get around this I used a copy and a Tcl pre proc

              set xlateOutVals [string replace $xlateInVals 0 1]

              • #116744
                Ben Ware
                Participant

                  What was your source value?

              • #116745
                Stewart
                Participant

                  It was an account number in the format of XX00000000

                   

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

              Viewing 3 reply threads
              • You must be logged in to reply to this topic.