Copy to Datatable is not a member of System.Array

[vikumars (vinoth kumar)]

Hi ,

I am facing the issue which is provided as a attachment

rowItem.Select.CopyToDataTable().DefaultView.ToTable(False, “User Name”, “Domain Name”)

[Manjuts90]

@vikumars What u exactly u doing in this statement.

[liu_shubin (Shubin)]

You can try your xaml file created by old version UiPath Studio. I also encountered the same issue in UiPath version 2018.3.0 but fortunately that my old version xaml file still works.

I suspected that the libraries called by different versions of UiPath Studio are not exactly same.

Sorry that I cannot upload sample file for you as I am a new user.

[sangasangasanga (sanga)]

Any solution?

[liu_shubin (Shubin)]

As stated in my previous reply, you can use old version UiPath Studio to filter a table and copy the data to another table. The file can be used in the new version of UiPath Studio. However, you cannot use .CopyToDataTable if you generate .xaml file using the latest version of Uipath.

It is quite weird.

Example:
Use Assign activity
TempDataTable =RawDataTable.Select(“[Column1]=‘good’”).CopyToDataTable

[sangasangasanga (sanga)]

but how can I use old version of studio when my studio auto updated to 2018.3

[loginerror (Maciej Kuźmicz)]

Hi @sangasangasanga

See here:

AsEnumerable is not a member of 'System.Data.Datatable'

Hi @lucas.mcgonagle EDIT 20.10 fixed this issue for newly created projects. You can fix it by adding the Assembly Reference manually in your xaml file: [image] Simply open the file in Notepad and create new line with this String: <AssemblyReference>System.Data.DataSetExtensions</AssemblyReference> Then reopen your project and the error should be gone. Please be careful while doing so and always keep a backup.

But also here:

Editing project files is not officially supported

Hi, We would like to remind everyone that manually editing project files such as project.json or the .xaml files is NOT an officially supported way of solving issues. It can lead to unexpected behaviours of Studio when interacting with your project. We cannot provide any guarantees that your project will continue to work after ill-advised changes. Please be careful. Thanks!

Please be careful

[sangasangasanga (sanga)]

So what you are saying is, I can add extension to my xaml file but also be aware after editing xaml file, there are chances it may not work, right?

[loginerror (Maciej Kuźmicz)]

Actually, I am quite confident that the solution will work in this case.

As to the warning/disclaimer, it is simply never advisable to edit the files unless you absolutely know what you are doing
If you stick to the solution above, nothing will break and all will go fine. Please keep your backups though, for a good measure.

[liu_shubin (Shubin)]

Filter Raw Data - Copy.xaml (8.1 KB)

You can use the file as a template. As said by logineror, the older version file includes different assembly references.

[mudit (Mudit rathore)]

addding the reference manually is also not working

[loginerror (Maciej Kuźmicz)]

Hi @mudit

What is your Studio version?

[karthikd8 (Karthik Deshpande)]

It is working when the reference is added manually. Check it!