Import excel to database plugin not working

I always always suggest using the related function provided by the Excel Tools plugin, fn!readexcelsheetpaging().  This allows you to build an expression rule that will convert the excel file to a CDT, then you can use the Write to Datastore service to persist the CDT to the DB.  This allows much more debugging capability and flexibility for converting values as they map to the CDT, etc.

You can upload a sample document to your environment and use it as a rule input to see the conversion occurring this way, much easier to work with.

Sometimes these smart services are finicky where a blank line or value can throw the whole thing off without warning.  This is easily avoidable with the function instead.

I always always suggest using the related function provided by the Excel Tools plugin, fn!readexcelsheetpaging().  This allows you to build an expression rule that will convert the excel file to a CDT, then you can use the Write to Datastore service to persist the CDT to the DB.  This allows much more debugging capability and flexibility for converting values as they map to the CDT, etc.

You can upload a sample document to your environment and use it as a rule input to see the conversion occurring this way, much easier to work with.

Sometimes these smart services are finicky where a blank line or value can throw the whole thing off without warning.  This is easily avoidable with the function instead.

Yeah ... but this can get you into scalability and memory consumption issues ...

Unknown said:

Yeah ... but this can get you into scalability and memory consumption issues ...

That is always good to consider, but I have not run into any of these issues in all my experience with this function which I use in a number of areas, starting when the function fn!readexcelsheet() was introduced.  Have you experienced any issues related to these?

I had such issues in the past and then switched to the CSV->DB Staging->Stored Procedure->DB Final approach.

It so much depends on the size of the imported file. And as the user uploads the file, I have no control, and users don't care.

I agree on the file size.  This is one of the main reasons I was glad to see the newer fn!readexcelsheetpaging() introduced where we can limit the batch size and loop if necessary.  All of my use cases are where users are limited to roughly a few thousand rows.  They can upload a 500 mb excel file if they like but I restrict how much of it will be read.