I would use a temp field to read the package number field and then make the package number field a calculation of temp+1.  This is assuming the first package is 0 and the second is 1 and so on.  Note the temp field would be the very first field in the right hand box

Hi BigLouie,

That is a cool idea, and seems straightforward. When creating the Temp001 with the Number Data Type I receive Error #26: Variable type invalid. Do you know why I'm getting this error? 

PackageNo is a string.  You have to convert your number to a text value, in the calculation.

Another thing you can try is change the Operation to Incr Assign with a default value of 0001.  It should always start with 0001 and if there is a second line it will assign 0002 and so on.  Or in your calculation NUM(Temp)+1

Thank you both. I'll try the Incr Assign with a default of 0001. 

Incr Assign does not work with our process as the packages are already created and that function created new packages with the tracking #s rather than assigning them to the already created packages. I'll test the calculation method. 

Edit: I needed to add 2 Temp fields. 1st temp field is String data type that reads the column data, and the 2nd is Number data type that converts the string into a number then adds 1. The PackageNo is a calculated field that converts the 2nd Temp field into a string. I'm going to test this and will update. 

Incr Assign does not work with our process as the packages are already created and that function created new packages with the tracking #s rather than assigning them to the already created packages. I'll test the calculation method. 

Edit: I needed to add 2 Temp fields. 1st temp field is String data type that reads the column data, and the 2nd is Number data type that converts the string into a number then adds 1. The PackageNo is a calculated field that converts the 2nd Temp field into a string. I'm going to test this and will update. 

If you can't get the VI job to do what you want, an alternative idea:

Run the CSV through a VBScript to read the file, loop through the lines, inserting a column with your package #'s (using pure file data logic, or even including an ODBC query to look at what package #'s exist for the invoice...), save to a new file (with the added column, and all original file data), then import from that new file.

Hi Kevin,

Thank you. I'll give that a try if the 2 temp fields idea above in my edit does not work. 

Another option:

Reach out to a Master Developer for some custom Perform logic.

After testing, this was the solution that worked best. A Task Scheduler to trigger the script was created for windows event id 4656 on the folder in which the file is stored.