I have a spreadsheet which I read using a REFramework without the Orchestrator queue. After reading the row I need to delete it after doing the necessary processing steps.
I tried deleting the current row and the row has been deleted. Only issue is the next row after the deleted row has been skipped.
As you are using ReFramework I suppose the bot is reading this data table in init state.
When the bot processed the current row in process state and remove it, the data table index changes, but the current Transaction Number don’t. It was incremented + 1
So
Let say you are processing row 100, the next one is 101.
But when you remove row 100, the row 101 changes to 100 and it already processed. Because this the next row is skipping.
My suggestion is add a new column at runtime using Add Data Column in init state
For each interaction, update this column (for rows that you want to remove)
Then at the end of your workflow, you use filter data table activity and remove the rows you don’t want anymore using this column as filter and finally remove the column too before save it.
When you say Add Data Colum in init state, do you mean add a column to the data table? And then for every run mark the row as processed as something which I can use when filtering the DT?