I have a big problem
in the REF when I upload some data by means of add queue item and then I want to process it, it processes it one at a time, when I want it to happen all at once, not if I let myself understand, let’s say I upload a table of the orchestrator data and then in process I want to work a simple log message log if there are 10 values in the table, the ten values will pass ten times as if there were 10 transactions,
I just want it to be a transaction, I want to upload a table of data and it’s just a transaction, is there a way to do it?
thank you very much if you can help me
if it is necessary not to use the orchestrator to do this as I told you, it would be fine
When you do that, in the REFramework solution, when getting the transaction item from the queue, one item will give a datatable of records which you can process. In other words, each transaction will have a datatable full of data which you can iterate and process in one go…
So, create a data table using build datatable and add the records you want to be processed under one transaction. and use that data table variable in the window I showed you in the previous screenshot as the input for Add Queue Item activity…
Yes… You can add the data to a data table using add data row activity…
So build the data table using Build Data Table activity
And then use a add data row activity to add the data into the datatable
Add data row activity has a input property called Array Row which you can use to pass in variables as an array so that you can add the data of the variables to the datatable as a row.
It should be written as:
{variable1, variable2, variable3} and so on…
If you want to add multiple rows to the datatable and the data is coming from variables, you can use a loop too.
well it looks a bit more complicated
and if I don’t use the orchestrator to record that data
there is a way that I can use the REF, since I have been testing that, and I get that there are no transactions and the process ends
is there any way to fix that
Thanks a lot
Yeah, you can use the REFramework without an issue…
So in REFramework, you get this error when there are not items getting assigned to the variable TransactionItem. As you are aware, after INIT state, Get TansactionData and Process states work one after the other and process is executed only if there is a value assigned to the TransactionItem variable.
So, check why it is not getting assigned by anything in the Get Transaction Data xaml file. You might need to use the debug option along with few breakpoints to understand what is happening…
i did that
in “init” at the time of reading my files I connected it to the “transaction data” variable to wait if I generated a transaction, but nothing ended the process and I did not enter “process”, then I did the same with “transaction item” and the same result is why I don’t understand
So in the init state, is the transactionData variable getting assigned with any value before the execution goes into get transaction data state? That’s one thing we need to check
The other thing we have to check is, in get transaction data xaml, whether it is getting the data from the Transaction Data variable, and also, whether it is reading the data properly from it to assign it to Transaction item…
The best way to understand what is going on is to use the debug mode.
That will, in any case, also change the “transaction item”, step from being “queue” to “data table”, I did it to prove more than anything
If it is not too much trouble, you could do that in the framework, something simple, that reads an excel in “init” and then in “process” through the “for each row” that writes the data of a certain column using "get row item ", and you pass me the zip over here to review it in detail
a favor, the thing is to detect the “transaction data” and go to “process”
I will here test with debug mode, just confuse me some terms of the REF
well it’s fine thanks, here is half a day
As I said simple, I just want to see what happens to process
read an excel and let that be the transaction
of course without using the orchestrator
