In Document Understanding , I was extarcting a value from exportDataSet by creating tw0 arguments variables in Export.Xmal. The argument are OUT in Direction. But those are becoming null when we came out from Invoke Xmal and not passing to external Varibles created in outside xmal.
Any leads helps me
Keep the variable name and argument name different
Don’t use same name bot will get confused
Ur current argument name looks fine
Change the variable name alone and try
hi
try by changing the names of the Variables as both the arguments and variables names are same
CustomerPO
InvoiceNumber
try this way once
cheers
That is entirely false. There is zero problem with having the variable and argument with the same name.
Put a Log Message activity after your Multiple Assign, and put a breakpoint on the Log Message activity. Run your process in Debug mode. When it pauses on the Log Message, verify if OUT_InvoiceNumber and Out_CustomerPO have values.
Yes it having values all the way to that xmal. Once i came out from Invoke Xmal thats where the values are becoming null. Basically i was extarcting these values from DU extarction table. That table is only exist in Export xmal. Once i stepped out from that xmal we don’t have access to that datatable
I was thinking because of that Main table argumenst are not passing outside of the table
It has nothing to do with the datatable.
Do the Debug suggestion I gave you and post a screenshot of the values in the debugging pane on the left.
Hi @Chaitan
If your outer XAML where you have invoked the workflow has variable and arguments with same name out_InvoiceNumber and out_CustomerPO. It’ll show null.
Can you check whether same name for variable and arguments is present where you invoked the export XAML
or to simply say if in the same XAML file you have same name for arguments and variables it’ll not work as expected.
Now can you place a log or breakpoint in the main-actioncenter file after your workflow is being invoked. and also check for same named arguments and variables in main-actioncenter
In your Main xaml, using universal search, search the variable names and see if you have them declared more than once.
It won’t pass the values if an exception is being thrown from your invoked XAML.
IF you need those values you would have to pass those values in your exception message.
something like
new BusinessRuleException(“invoiceNo:”+out_InvoiceNumber+“;CustomerPO:”+out_CustomerPO+“Unable to proceed due to some reason.”)
new Exception(“invoiceNo:”+out_InvoiceNumber+“;CustomerPO:”+out_CustomerPO+“Unable to proceed due to some reason.”)
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
