Pentaho

I test the transformatios with PDI 8.1, the follow pic is the result:

In addition, you can use the step "Get System Info" to get what system info you want.

This is the step wiki : https://wiki.pentaho.com/display/EAI/Get+System+Info

Hi Winson,

Thanks for your awnser.

This is not the behaviour I was talking about, I'll try to explain it with an example.

c:\tmp\job.kjb:

c:\tmp\TransformationDir\transformation.ktr

If you run this Job in PDI 8.0 you get -> c:/tmp/TransformationDir

And running in PDI 8.1 -> c:/tmp

You are right, ${Internal. Entry. Current. Directory} in version 8.1 is, indeed, to perform the job's path.However, versions 8.0, 8.2 and 8.3 are the path of job/Transformation where the variable is located

so please do not use ${Internal. Entry. Current. Directory} in version 8.1

FYI

https://help.pentaho.com/Documentation/8.1/Products/Data_Integration/Data_Integration_Perspective/Run_Modifiers/Variables

Ok, thanks, We will try to upgrade machines to version 8.3

In the 9.0 we notice the same behavior of the 8.1, seems a regression, the Internal.Entry.Current.Directory assume (gran)parent job path instead of current

I've experienced this issue with 9.0 also. But, oddly, it was working for me in 8.1.0.0-365

${Internal. Entry. Current. Directory} in version 8.3.0.8-718 is not working as expected in sub jobs.It always replacing variable with hard coded path in server with master job pah and unable to find sub job after saving it.Any help please