Page Operations
Browse SpaceDescription
This step returns rows that were previously generated by another transformation in a job. The rows were passed on to this step using the "Copy rows to result" step. To allow you to design more easily, you can enter the meta-data of the fields you're expecting from the previous transformation in a job.
(!) *Important*: no validation of the supplied metadata is done at this time to allow for greater flexibility. It is just an aid at design time.
Now I understand that I cannot expect this step to work when executing the transforms on different slave servers, however I am expecting this to work when everything runs on the same slave server and there is 1 job that call both transformations which are "sharing" the data.
Am I making the right assumptions?
An example usage of this step is getting a list of files to process in one Job Transformation step then passing the list to another step. The way you would access the filename in the second Job Transformation step is to add the "Get rows from result" step. Then edit it and add the fieldname "filename" in the "Fields" table.