-
Title
Automation Designer action, run with specific parameter file, works when launched within Toad, but not from command line. -
Description
In Automation Designer, a simple app is created, which contains a single 'export dataset' action.
Create a parameter file for that app 'param.ini'
Copy the parameter file to 2 other names and edit them to produce different results.
Within Toad, it's possible to run the action using the specific parameter file required and the results are correct.However, when running the action from the command line, the result is not using the correct parameter file:
"Toad.exe" -c uname@dbname -a "App1 | C:\Toad_Export\param1.ini" actually runs the initial param.ini file instead.
-
Cause
The connection switch '-c' is not designed to be used in conjunction with a parameter file. If '-c' is used, then Toad will use the output bound to the action (in the above example param.ini) and ignores the parameter file (param1.ini) -
Resolution
Remove the '-c uname@dbname' from the command line argument i.e. "Toad.exe" -a "App1 | C:\Toad_Export\param2.ini"
If another connection is required that is different to the one bound to the action, then this can be amended within the parameter file. e.g.
"ConnectionCount=1
Connection_1=scott@dbname1"