ADF created an extra blank row between header and 1st row of data (in csv file)

Question

I am trying to not have an extra blank row after the header.

Currently, the process is that ADF grabs a csv file from Azure file share, and move this csv file to a folder in that same file share hierarchy.

Basically, I am just trying to archive files from original file structure to certain folders (of year and month).

Is there any configuration that I could do to prevent this happening (created an extra blank line)?

I found difference of data from the original csv file and the one that was moved.

The last column (Hourly Rate) for the destination file has more character.
I am not sure whether issue is anything to do with difference of output from this particular column.

Original:

After moved:

The mapping is String --> String.

Answer 1

Hi @Anonymous ,

Thankyou for using Microsoft Q&A platform and thanks for posting your question here.
As I understand your issue, while copying the data within Azure FileShare using ADF, a blank line is getting added , which is not expected output. Please correct me if my understanding is wrong.

Kindly try executing the pipeline by provide 1 in the skip line count option in the source settings

For more details regaring SkipLineCount property, kindly check: Copy activity properties

Regarding the format of column 'Hourly Rate' , it should not be the reason of adding an extra blank line, however, if you want to trim the end characters (0) in the column values, then you need to go with Mapping dataflow to achieve the same.

Hope this will help. Please let us know if any further queries.

------------------------------

• Please don't forget to click on or upvote button whenever the information provided helps you.
  Original posters help the community find answers faster by identifying the correct answer. Here is how
• Want a reminder to come back and check responses? Here is how to subscribe to a notification
• If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators

Answer 2

@AnnuKumari-MSFT
I was able to find the solution by just correcting the "File path type".

Before I used the same(or shared) "File path type" with other pipeline.

I will not use "Wildcard file path" again.