Is there any documentation for running powershell scripts with TDP?. We've been having to use a batch file to call powershell because TDP seems to have issues calling it directly. The approach works, but it seems like an unnecessary step since TDP accepts arguments.
We're also trying to suppress the header output from MFT when we call it to move a file. When TDP runs the script MFT runs, but the header is being written to standard error and it shows up in the output logs.
MFT Error Message: TIBCO Software Inc. (R) 64-bit File Transfer Client for Windows
No documentation that I know of for executing Powershell commands/scripts within TDP automation flows. Might have to get detailed clarity from one of our SME... probably on the Dev side.
As an alternative to consider, is it feasible to embed TDP calls (commandline) within your Powershell, instead of the other way around?
I this scenario TDB only needs to load data and then call another script to kick off a managed file transfer application, so there would be no need to call TDP. Wrapping it in a batch script works for now, but I would like to figure out why Powershell is having trouble receiving parameters from TDP.
Probably going to need some insight from one of our SMEs, or perhaps other TDP users who have figured out work-arounds for projects similar to yours... hopefully we can get one of our Dev guys to chime in here...regardless, they may need more details on your automation work flow...
Hello Toad.User,
Toad Datapoint's Automation Run Program activity is leveraging .Net framework Process.
Here is the documentation: Process.Start Method (System.Diagnostics) | Microsoft Docs
In Theory you should be able to invoke powershell.exe interpret directly:
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -noexit -file "C:\pscript.ps1"
Unfortunately, Run Program activity wasn't designed for this use case and changes in activity validator needs be done.
For now the .bat file workaround is probably the best solution.