August 23, 2014 at 10:07 pm
I have an SSIS package that basically does ETL on an Excel file then outputs everything into a new Excel file.
As an example, let's say my original Excel file has 50 rows. My resulting Excel spreadsheet has 52 rows after ETL. It's somehow picking up on what I assume are 2 rows somewhere in the original Excel spreadsheet that appear empty but have some white space or something.
Is there a way for example to say that I only want to export rows that contain a 9-digit social security number? That way, if there are a few "dead rows" with white space or blanks or something, they won't be exported to the final Excel file.
Thanks for any recommendations.
August 24, 2014 at 1:32 am
brad.mccollum (8/23/2014)
I have an SSIS package that basically does ETL on an Excel file then outputs everything into a new Excel file.As an example, let's say my original Excel file has 50 rows. My resulting Excel spreadsheet has 52 rows after ETL. It's somehow picking up on what I assume are 2 rows somewhere in the original Excel spreadsheet that appear empty but have some white space or something.
Is there a way for example to say that I only want to export rows that contain a 9-digit social security number? That way, if there are a few "dead rows" with white space or blanks or something, they won't be exported to the final Excel file.
Thanks for any recommendations.
One way is to add a Conditional Split to your dataflow. Redirect any unwanted rows to an unused output - job done.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
August 25, 2014 at 8:29 am
The conditional split was exactly what was needed. I placed a rule/filter in the conditional split to only export rows that had a 9-digit social security number into the finalized Excel spreadsheet. Many thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply