this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: Bingdom
User Name: Bingdom
Forum Rank: Newbie
Real Name:
Location Australia
Gender: None Specified
Joined: Monday, May 17, 2021
Last Visit: Thursday, May 27, 2021 3:00:23 AM
Number of Posts: 2
[0.01% of all post / 0.02 posts per day]
Last 10 Posts
Topic: Result doesn't pass for error/success handling
Posted: Thursday, May 20, 2021 2:35:45 AM
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.

Topic: Result doesn't pass for error/success handling
Posted: Monday, May 17, 2021 10:06:36 AM
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?

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.