How to split datatable into multiple datatables, using empty row as seperator

I have a datatable which i need to split into multiple data tables using empty row as seperator

@nikhil.s
find some starter help here:
DT_Slice_ByBlankRows.xaml (10.0 KB)

it is calculating the row indexes for the blank rows and is slicing the datablocks with the help of skip() and Take() method.

Let us know your feedback

1 Like

can we take each splitted table’s first row as header?

the splitted datatable already should have same column headers as the datatable from it was split.
Just check it within a debug run, setting a breakpoint inspect it within, locals, watch or immediate panel

input

actually my input scenario is given in excel sheet i need to read them as different tables. there rows dynamically changes depending on the input. columns varies from table to table.
Can we do this type of problem

was not provided in your requirement description. Here was only mentioned that it is to split on empty rows.

In such case

  • we do write a correction run, will use first line for header name reseting/adoptions
    Or:
  • we do the slicing on a different strategy and try to calculate the different excel ranges for readin

splitting is limited in input sheet is it possible ?
To read them from excel to different tables using empty row as seperator??
If possible can you please suggest me a way out

Using this I am not getting the exact output…I have 5 data tables in a sheet and i want split those and write it down in word…after using above code first data is splitted then first and second, then first second and third…like this it is getting splitted

Hi PPr,

Kindly find the below screenshot FYR, I also need to divide these 2 and write the below 2 datatables into different sheets by using empty row as a separator…datatables is constant but rows are dynamic

and in the above code which u had attached earlier, the below activity is not visible. Can you please tell me which are those.

@bhanu.priya2
may we ask you to open a new topic for it. So we can better keep clean scenario and suggested solution. Thanks