Thanks--


I'm confused--if tcontextload is saying that the context has been updated to reflect a new value (i use the print option), why would that value not be actually used in the toutputdeliminated node?  I'm not trying to change the default value itself, I'm trying to use a different value in the job itself, dynamically set by the tcontextload node.

Could it be the case that context variables updated in the job do not apply to toutputdeliminated nodes?

The screenshots below are out of order (couldn't figure that out), but show:

the job execution--you can see that the default context contains a filepath that is different from the one updated by context load (in the run window).
the configuration of the toutputdeliminated node
the resulting file written to the desktop (which is not the name of the file in the updated context).

Sure, see below.  Thanks for the reply.

This is just a test job I am using to understand the functionality.  The default context remains active even though the log pane says its been updated.

Thanks,

Michael

Hello,

I am using a context variable to dynamically update the output directory in a toutputfiledelimineted node.  I am using tcontextload to update the context variable.  I have the tables set correctly and the run window says:

tContextLoad set key employer_id with value 'C:\users\mvucovich\desktop\test_out.csv'

However the file is written to the path set as the default for that context variable, not the directory above.  I'm quite confused because it appears that the context variable (employer_id) has been updated according to the log, but is not actually passing the value.

I am running Windows 7.

Thanks,

Michael