Hi vangelis.kouzounis-itt,
As far as I know, the "Unable to create new row" error is a standard error thrown by the web part when it is not possible to map the columns from the Excel file to the custom table fields. Check the Event log, there should be the error event logged with additional details.

Hi,
I am using this Web part to import an excel file but getting the below error

Error: Unable to create new row.

Any help is appreciated
Thanks

I get "Error: Failed to upload file." May I know what is the exact issue?

I have an interesting story to present here about this web part.
First of all, great idea and its working ...so, thank you.
Now, I had lot of compilation issues with this webpart.
Environment used: Windows Server 2016, Visual studio 2017
1. Imported the web part objects
2. Move the artifacts to CMSWebParts/[custom folder]
3. Encounterd multiple errors.
So, I copied the ascx and the code behind files to some other folder outside of the Kentico folder
created a web part (Kentico gave a long class name -- keep as it is)
copied the ascx code and the code behind (just the logic) seperately into the web part class (DO NOT change the class name)
compiled
Now its working as expected.

Hi Andre,
have you ticked the "Import code files" check box when importing the web part? (See also my comment from Mar 27, 2015).

I imported the zip file and when viewing a page that has the web part on the admin area, I get this message:

Error loading the Webpart CustomTableDataImport of type CustomTableDataImport

Does anyone know why?

Imported my Excel files for the custom tables with no issues at all. Nice utility!

Hi Paul and Sanket,

I tried to take a look at the issue you have mentioned and I think I have found a solution. The problem is in the CustomTableDataImport.ascx.cs file on the line 246: attributes.Add(col.Attributes["r"].Value.Substring(0, 1));

For columns with longer names (AA, AB, AC, ...) there should be Substring(0,2)

So you can easily fix this e.g. by adding a columns counter and simple if-else condition in the code. Something like this:

var i = 0;
foreach (XmlNode col in cellNodes)
{
dt.Columns.Add(sharedNodes[Convert.ToInt32(col.InnerText)].InnerText.Trim());
if (i < 26)
{
attributes.Add(col.Attributes["r"].Value.Substring(0, 1));
}
else
{
attributes.Add(col.Attributes["r"].Value.Substring(0, 2));
}
i++;
}

If you find some nicer solution, feel free to share it with others here.

Hi,

I am also getting the same issue as Sanket Shah. Everything works up A - Z for not afterwards!

Hi,

I am trying to export the excel sheet having 100+ columns. It is inserting the first "A-Z" columns properly but "AA" column onwards are not properly inserted.
"AA-AZ" are repeating the value from the A column, "BA-BZ" are repeating the value from B column and so on.
After Debugging, I found that while reading the excel sheet, the "attributes.Add" in "ReadExceldata()"function repeats the values from 26th index onward.

How do I change the attributes at index[26] and make it AA,AB,AC and so onward?

jnarkar-imediainc: I tested the web part on Kentico 7 with .NET 4.0 and it worked properly. I assume that you just need to add the assembly mentioned in the description above into your web.config file.

dani: Just import the web part into Kentico using the Import wizard. For more info, see the Kentico documentation https://docs.kentico.com/display/K82/Importing+a+site+or+objects

ashish: I would be glad to help you, however, I wasn't able to reproduce the error.

Any instruction how to add this to our project? plz

I am working with Kentico 7.0 and System.IO doesn't have type or namespace for packaging. I would need alternate for .net 3.0 for kentico 7.

server not found error in custom table edit option when data option is clicked

Hi chetan2309, try to import the web part again and in the Step 2 of the import process tick the "Import files (recommended)" and "Import code files" checkboxes. It could do the trick.

I am getting this error in event log after adding this web part on my page. The webpart was added successfully

I took 8.2 build. kentico I have is 8.2.2 on Azure.

Message: The file '/CMSWebParts/MyWebParts/CustomTableDataImport.ascx' does not exist.

Marco: Maybe I don't understand properly when exactly you are getting the error. I tested it on both Kentico versions (7.0 and 8) and it worked well. Please, submit the question to our support by filling this form: http://devnet.kentico.com/support
with a note that this ticket can be assigned to me. We can discuss it in more details.

Hi Daniela,
I am still trying this, sometimes it passes through, sometimes not! I have set existing folders and tested many times, always getting this strange error most of the times. Is this a quick fix for Kent-X?
Thanks,
Marco

Hi Marco,
you are right, now I got this error in 8.0 version too. It seems that there is some problem with saving macro in the "File Storage Path" field in the web part properties. Remove the macro by clicking the small cross mark next to the field and enter a basic path like "~\foldername" there.

Hi Mario,
there is no documentation for this web part but it is very simple to use, just read the description here.

I am getting this error when setting the Web Part

The entered values cannot be saved. Please see the fields below for details.

File Storage Path: Please enter a value.

Can I get any help?

Where is the documentation for this ?

Just your custom fields. Kentico fields like 'Created date' or 'GUID' should be filled automatically just as when you create new item in UI.

Thanks Daniela. I will look at the property.

Do I need to include standard Kentico fields in the spreadsheet too? Or just my custom field code names?

Hi Mark, entering virtual path like "~\CMSImportFiles" in the web part properties should solve your problem.

How do you set where the file is uploaded? I'm getting an error that says "E:/sitesroot/0/CMSImportFiles/<filename>.xlxs is a physical path, but a virtual path was expected."

Do I need to include standard Kentico fields in the spreadsheet too? Or just my custom field code names?

You all rock, thanks for this!