Is it possible to store it
datatables will be same but data changes
i use for each and
ex
In first iteration
code amt
A001 500
A200 500
B100 100
second iteration
A006 500
A500 500
B300 100
dynamically depending on for each i wil give datatables
but i need output in one data table
Code AMT
A001 500
A200 500
B100 100
A006 500
A500 500
B300 100
Can we do it
as mentioned the merge datatable activity should help
sorry im new to these data table activities
data table name will be dtCode
in merge activity what should i use as source and destination
im new to these data table activities
data table name will be dtCode
in merge activity what should i use as source and destination
can you elobarate it please
Hi @nikhil.s
The steps are as follows-:
Declare a DataTable with empty rows and that will be your Destination DataTable,
Second DataTable will be your variable DataTable (Which is Source DT in Merge activity)
The output Destination will contain final DataTable.
If this helps mark this as solution.
Happy Automation!
Regards,
Aditya
I will use filter datatable inside for loop, which dynamically changes inside values and gives output a datatable on each iteration of loop. i need to store each table in each iteration into one table. But using Merge is only giving last datatable output
@nikhil.s
recheck your implementation that it is not doing an unwanted overwriting leading to the result to get only the last datatable.
Your requested scenario was more often implemented in our projects and merge datatable did the job.
Yes you are correct, It is making an unwanted overwriting, I found a fowl in my implementation! Thank you!
Thanks Peter. Just checking, what if there were three tables? It appears you merged dtUp… and dtAll into dtAll, but what if there was a third table, what would you do?
how to know if there is unwanted overwriting because i am experiencing the same issue and not sure how to rectify
@Raja_Muthu
Welcome to the forum
Just open a new topic for your case and get individual help. Please give us as much details as relevant for the case (sample data, what was modelled so far…)