LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: UisceBeatha

Hi,

I've come across an issue where I'm importing a number of Excel spreadsheets from a directory. We have a directory list node attached to the Excel import and this all works okay however if one or more of the spreadsheets have extra columns they doesn't get imported but no error appears in the import node to notify us of this. Is there a way to force the import node to error if it can't import all the spreadsheets?

I'm using BRE version 4.5.2

Many thanks

Barry

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hi,

What you are looking for is handled by the "ConcatenationType" parameter.
If you set this to "Exact Error" then you will get the error you want.

However, the ConcatenationType parameter has some other useful options which might help further...

You could set the ConcatentationType to "Intersection" to get only the columns that appear in all of these worksheets, or "Union" to get all columns that appear in any worksheet.

If you set the ConcatenationType to "Exact New Output", then add another output to the node, and give it some name (e.g. "metadata"), then set the "MetadataOutputPin" parameter to the name of that output (e.g. "metadata"), then all worksheets that have exactly the same colulmns as the worksheet in the first workbook will be output to your existing output, but each of the worksheets in the other workbooks that don't match this metadata exactly will be written to a separate BRD file. The name of each of these worksheets, the excel file from which they came, and the location of the output BRD will then be written to the "metadata" pin.

Hope this helps,
Tim.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: UisceBeatha

Hi Tim,

That's for your quick reply - that works perfectly!

I've come across another instance where a similar issue happens (i.e. one Excel file doesn't get imported but no notification) however this time it looks like it's because the worksheets have different names. Is there any way to get the node to error when it can't import the Excel file with the sheet name which differs?

Thanks again for your assistance.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Sure,

Use the "UnmatchedOutputNameAction" parameter - in the "Exception Behavior" tab.