Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We're working on upgrading to Tidal 6.0.3, and we've run across a few issues. However, our biggest issue is that the new transporter seems to drop group variables when we're migrating job groups up (Dev->Test->UAT->Prod). Variables in jobs themselves...
For us to get Powershell to work in Tidal we had to create a command file with the call to the powershell executable and pass the powershell script to the command file. The command file itself is simple::: Starts localization of environment variable...
Excellent! I was hoping we weren't the only ones, and it's even better that there may be an existing patch out there. I've submitted the SR and will let you know if this does the trick.
