Skip to main content
dinesha5713
dinesha5713
December 3, 2024
Solved

Save Into vs Target

  • December 3, 2024
  • 1 reply
  • 0 views

/resized-image/__size/640x480/__key/communityserver-components-multipleuploadfilemanager/99091518_2D00_115d_2D00_416d_2D00_a0fb_2D00_2f8360c6673f-289184-complete/pastedimage1732717760969v8.png

Here i queried some detail ,it is in Ac in input tab but not give Save into , in the output tab(img 2) im updating the Ac value and storing in the Target

in this case it is working fine

but in the input tab if i give the Save Into the value is not updating in the output tab

both Save into and Target given only the Save into come out of that Script task or what

Best answer by mikes0011

you can't have the input and output tabs both save into the same target PV - there's no guarantee as to what order the saves will execute, and you should assume they'll execute in random order if both are configured.  In your case you will ALWAYS want to ONLY have the save target configuerd in the OUTPUT tab.  I usually don't even configure a value in the input tab, instead doing any required calculation (etc) in the expression of the output itself. You can use local variables to help you, for the case where you're querying stuff.  And if it gets too complex, you can always migrate it to an Expression Rule for easier testing.

(FWIW, The one case where I make an exception to this is if I need to query / configure a complex evaluation in the input and then use the same value in several different output values - in this case, doing it in the input tab means it isn't done repeatedly in the different outputs.  But all other times, I just configure all the info in the output tab only.)

1 reply

mikes0011
mikes0011Answer
Brainy
December 3, 2024

you can't have the input and output tabs both save into the same target PV - there's no guarantee as to what order the saves will execute, and you should assume they'll execute in random order if both are configured.  In your case you will ALWAYS want to ONLY have the save target configuerd in the OUTPUT tab.  I usually don't even configure a value in the input tab, instead doing any required calculation (etc) in the expression of the output itself. You can use local variables to help you, for the case where you're querying stuff.  And if it gets too complex, you can always migrate it to an Expression Rule for easier testing.

(FWIW, The one case where I make an exception to this is if I need to query / configure a complex evaluation in the input and then use the same value in several different output values - in this case, doing it in the input tab means it isn't done repeatedly in the different outputs.  But all other times, I just configure all the info in the output tab only.)

    Terms & ConditionsAccessibility statement