Cant assign value for imported argumets in invoked workflow

Hi,
I’m currently doing the RPA Advanced Developer Training Course. I cant assign values to the imported arguments in the invoked workflow. I’ve saved the output of the same workflow in an ‘out’ argument. But this argument is not showing up in the value field and is throwing an error. What might be the problem?
Screenshot (23)

Whats the specific error which is showing up? There might be a chance of Variable has been created in Inner scope and you have selected the outer scope and hence not visible, Check with global search options.

Hi @Midhun_Pc

I think it is about the argument variable name.
In Acme_Datascraping xaml file in Arguments you have workItmes as out argument.
But in GetTransactionData it is Out_workitems as out argument.

can you please click on import button in GetTransactionData where you are invoking Acme_Datascraping.

Ragards,
Vijay.

The alert pop up shown is this- varname is not declared. It may be inaccessible due to its protection level.
I’ve assigned the output datarow to an out Argument in the ACME_DataScraping.xaml workflow, there is nothing wrong in that, right?

inaccessible due to its protection level. - Its just the scope issues then.

I’ve assigned the output datarow to an out Argument in the ACME_DataScraping.xaml workflow, there is nothing wrong in that, right? - definitely there is no issue. Just make sure about the type of the Argument.

I’ve used DataTable.Select operation which returns a data row. So the workItems argument is of type array of system.data.datarow.
How can i solve the scope issues?

In ACME_DataScraping.xaml file there is a click activity followed by data scrapping. The data is stored as a Data Table which is then filtered by dataTable.Select method which returns a datarow which is assigned to the workItems argument. So for this workflow there is no in argument. This workItem argument is then passed to the GetTransaction work flow to an if activity where it is met with an condition and is assigned to out_TransactionItem in the framework.

Is there any error in the direction and naming of the arguments?

if the direction is out can we have two different names for same argument …???

i think it should have same name in both xaml files.

@Divyashreem - please correct me if i am wrong on above explanation. :slight_smile:

Regards,
Vijay.

Can you send me your project and the workflow details??

Calculate Client Security Hash - Process Design Document.pdf.pdf (483.6 KB)

Calculate Client Security Hash - Walkthrough Hints.pdf.pdf (1.3 MB)