|
Rank: Newbie
Joined: 5/17/2021 Posts: 4 Location: Australia
|
Hey all,
Essentially, it appears that the result for the first execution step doesn't pass down to the handler as the image depicts below.
Is there an existing workaround?
|
|
Rank: Member
Joined: 2/3/2016 Posts: 17 Location: Plymouth, Michigan
|
You should be able to get the output of the Error Handling step by declaring a variable (for lack of a better word), in the 'Assign this step's result to field.
This screenshot shows an example of it.
Hope this helps
|
|
Rank: Newbie
Joined: 5/17/2021 Posts: 4 Location: Australia
|
wriley wrote:You should be able to get the output of the Error Handling step by declaring a variable (for lack of a better word), in the 'Assign this step's result to field. This screenshot shows an example of it. Hope this helps
Hey, Thanks for the tip.
Doesn't help too much, unfortunately.
I've noticed I can move it out of the error handling, and the variable would carry over.
I don't want to introduce the error handling through the program I wrote. It would be nice to keep everything as close to the Altova products as possible (don't need some else to specialise in both Altova and programming if I were to leave).
Maybe I should report it as a bug.
I noticed I can retrieve the variable from when it's outside the scope of the error handling. Very weird.
|
|
Rank: Advanced Member
Joined: 2/27/2009 Posts: 558
|
It's by design. Per the documentation, "one cannot refer to the result of a step that's within a protected block, from the exception handler…It doesn't matter if the exception handler is On Success, On Error or Always."
|
|
guest |