@david-burgess
Forum Replies Created
-
I ran into the same issue. I had to take my list and used a COPY statement with source @myList –> @myIterationCnt and the used the following code in the pre-proc:
<pre>set dummyList [split [lindex $$xlateInVals 0] ]
set dummyList [llength $dummyList]
set output “”
for {set i 0} {$i < $dummyList} {incr i} {lappend output $i}
set xlateOutVals</pre>
After this my variable @myIterationCnt would contain 5 entries {0 1 2 3 4} if my list had five entries. I could then use @myIterationCnt as the variable in the iterate. This solved the iterate issue, but you then have to pull out the actual value yoyu want from your list. To do that, I have a COPY statement inside the iterate, that has two values on the input. $%u1 and @myList. The target of the copy is my output field, but I have the following code as a pre-proc in the COPY statement:
<pre>set index [lindex $xlateInVals 0]
set drugList [lindex $xlateInVals 1]
set drugList [split $drugList ]
set returnValue [lindex $drugList $index]
set xlateOutVals</pre>
This works because both code blocks in the pre-proc knows to respect the curly braces, while the iterate does not. Hope this helps, sorry I didn’t update the thread when I ran across the issue myself. If you are confused I can try to grab some screen shoots of my setup tonight or tomorrow.
