Argument not passing value outside xaml

[Shreya_Rao1 (Shreya Rao)]

I have created 1 argument with out direction and assigning the value to that argument in Exception block of the code so that if any exception occurs that argument will be assigned with some value and can be used after rethrowing of the exception to outside

But somehow that value is empty in outer xaml.

Can anyone help me with this?

[Yoichi]

Hi,

Can you share your workflow?

Regards,

[ignasi.peiris]

Hi @Shreya_Rao1 , please look at this thread, where something similar was discussed:

Doubt in Arguments

Hi @Sudharsan_Ka , I see you are ending with a Throw, this means that normal arguments do not normally work within that Try Catch. If you want to pass out info to the Main workflow, coming from an error in the try, you need to 1st init a DataTable or a Dictionary in the main. Set it as In/Out inside the Process.xaml, and then fill it inside. Normal “String Out arguments” do not carry information out of the TryCatch. Please try it and update us! Best Regards, Ignasi

It seems that you’re filling the variable in the “Catch” part, and therefore it should get filled, but nonetheless, changing that variable to some structured type like dictionary, or DT, might be worth a try.

Best Regards,

[fernando_zuluaga]

Check if you don’t have any other variable in another scope with the same name, also check whether is the same type of data

If it’s possible share your workflow please

Regards

[Veera_Raj (Veeraraj Sethuraman)]

please attach xaml

[Shreya_Rao1 (Shreya Rao)]

Sharing Test Workflow. I am doing s
Test_Re.zip (985.2 KB)
ame thing in My project workflow

[Debakanta_Mahanta]

Hi Shriya,

you can do same in alternate way
create exception argument in Process.xaml

you can throw same in main.xaml

check attached solution.
Test_Re.zip (985.5 KB)

[Yoichi]

Hi,

There are 2 points to take care, I think.
First, if some exception is thrown (or re-thrown) in callee xaml, Out type argument is not assigned as a result, even if some value is assigned in callee xaml before then.

Second, if some exception is thrown in callee xaml, it’s immediately caught by try-catch activity in caller xaml when it exits from callee xaml. So in this case, WriteLine activity just after InvokeWorkFlowFile activity won’t run.

So, I think it might be better to use Exception.Data as the following. It can add any message to exception instance, and get it in caller xaml etc.

Test_ReV2.zip (985.2 KB)

Regards,

[ushu (Usha kiranmai)]

@Shreya_Rao1 According to your statement, when an exception occurs the argument was assigning with a value, correct but since you are re-throwing that exception it was returning an empty value

The argument returns the updated value or assigned value only when the workflow successfully processed. Otherwise, it returns a empty or last run value

In this case, instead of assigning value to the argument , after re-throw you can use exception.Message which gives the exception reason