Hi Mates,
While doing my development of a BOT, It had to read a single row of a data table and load that data into orchestrator queue as a transaction. In order do that I need to do convert Datarow into Queueitem.
I am Failing when I am trying like in the snippet is failing, Is there a way to do so?
Hi,
If you need to upload datarow to queue of Orchestrator, how about using AddQueueItem activity?
Regards,
A Queue Item is not just name/value pairs. The .SpecificContent property is name/value pairs, but there are other properties of a Queue Item.
If you have a datatable just pass the entire datatable to the Bulk Add Queue Items activity, and it’ll do the conversion for you.
Hi @postwick, Thank you Mate for trying to resolve my issue.
As per the project guidelines / Limitations I am only allowed to add one row once.
Hello @Yoichi, Thank you Mate for trying to resolve my issue.
The Objective here is to Convert a data row into Queue Item, Then the same should be used in the setTransactionStatus. No Interaction with Orchestrator Or Queues. It is all with in Project. RE Framework should be used without changing the schema and not including Orchestrator queues. That’s why i am converting my input Data Table each row picked and processed.
If so then you need to change the transaction item type to Datarow and then in the process xaml you can use add data row
basically it looks like the dispatcher process where each item is added to queue…for ref to work as dispatcher you need to change the transactionitem type as you need from the queueitem type which is suited for the performer piece
Even if you dont want to add items to queue still if you want to process from datatable onlye ven then you need to convert the transactionitem appropriately
Hope this helps
cheers
This course teaches you all the changes to make in REFramework so it will work from a datatable instead of a queue.
Thank you @postwick, Will go through it.
Thank you @Anil_G
Then, I need to change every xaml the ‘TransactionItem’ type to ‘DataRow’ & have to do changes across the project where all it used. Let me learn recommended by @postwick
To summarize changes are there in 4 xamls …main,get transaction data,process xaml…set transaction status…and if you dont want to use set transaction status to write the status to excel or somethere then no need to change that at all…just pass nothing to transactionitem and you are dont for that
Cheers
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.