I found this question in earlier posts, but without a clear answer. I have a transformation which is using a calculator step. The calculator step creates a new field called "full_path". The transformation runs fine, but when I put it into a job, the job returns the error: Calculator.0 - ERROR (version 4.4.1-GA, build 18329 from 2013-04-17 12.31.49 by buildguy) : Unable to find the first argument field 'full_path for calculation #1.
I have tried making it a global variable and an argument, but I get the same error in the job. I have also tried "Set variable". No problem running it in the transformation, just as part of a job.
The transformation has a text file input step which reads approximately 5,000 text files from several folders, searches for a particular string and returns the string each time it finds it, along with the path and filename of the file that contains the string. I am also using the Additional output fields tab in this step - that is what returns the filename and path.
The next step is the calculator step which takes the two additional output fields from the previous step and uses them to create the new field called "full_path".
I then have a step to return only unique rows (the data comes in already sorted).
And finally, a step to output the result to an excel file.
All of that runs fine until I add it to a job, then it will no longer run.
I have tried making it a global variable and an argument, but I get the same error in the job. I have also tried "Set variable". No problem running it in the transformation, just as part of a job.
The transformation has a text file input step which reads approximately 5,000 text files from several folders, searches for a particular string and returns the string each time it finds it, along with the path and filename of the file that contains the string. I am also using the Additional output fields tab in this step - that is what returns the filename and path.
The next step is the calculator step which takes the two additional output fields from the previous step and uses them to create the new field called "full_path".
I then have a step to return only unique rows (the data comes in already sorted).
And finally, a step to output the result to an excel file.
All of that runs fine until I add it to a job, then it will no longer run.
