title: Error using relative paths in Alteryx when running through Powershell
body: <p>I have a Powershell script which calls an Alteryx analytic app (wizard) and inputs a single parameter into it via an .xml - method used to do this is <a href="https://help.alteryx.com/2018.3/Command_Line.htm" rel="nofollow noreferrer">here</a>. </p>
  
  <p>The output tools in the Alteryx workflow are setup as relative paths to store outputs to an <em>Input</em> and <em>Working</em> folder which are a level above the app itself, e.g.:</p>
  
  <pre><code>..\Input\FileName.yxdb
  </code></pre>
  
  <p>If I open up the Alteryx workflow and run it, or run the app via the interface, it works absolutely fine and my outputs are stored correctly. However, running it through Powershell using the code,</p>
  
  <pre><code>$modules = "C:\Projects\2019\Modules"
  cd $modules
  AlteryxEngineCmd.exe .\Extract_Variables.yxwz .\_Version.xml
  </code></pre>
  
  <p>returns the following errors:</p>
  
  <pre><code>Error - ToolId 5: Cannot access the folder .\Input\.
  Error - ToolId 15: Cannot access the folder .\Working\.
  Error - ToolId 24: Cannot access the folder .\Input\.
  Error - ToolId 26: Cannot access the folder .\Input\.
  </code></pre>
  
  <p>despite the relative paths working fine if run directly inside the workflow. Powershell will run the Alteryx workflow okay but it fails to save the outputs.</p>
  
  <p>As a test, I moved the <em>Input</em> and <em>Working</em> folders to the same level as the app itself and this worked fine - the files save to these test folders - so it is as if Powershell doesn't understand the two dots to represent moving up a level. In fact, I can write</p>
  
  <pre><code>..............\Input\FileName.yxdb
  </code></pre>
  
  <p>and it would still output to the test Input folder I created alongside the Alteryx app itself. Anyone know why this is the case?</p>