Hi Brian,

What’s the PowerBuilder version you are using? PowerBuilder 2019 R3 build 2728 and PowerBuilder 2021 support passing parameters to the EXE directly. Please download and install it to verify the issue and let us know if any problems.
You can get the installer from our Downloads portal at
https://account.appeon.com/download/2019 (login required).

Please note if there are multiple parameters, you need to put them between double quotation marks or replace the space between parameters with another character, for example:
C:\Users\user_name\AppData\Roaming\PBApps\Applications\localhost_app\app.exe "parm1 parm2 parm3"
C:\Users\user_name\AppData\Roaming\PBApps\Applications\localhost_app\app.exe parm1/parm/parm3

Regards,
ZhaoKai

Here is how command line parameters work in PowerClient/PowerServer:

If the parameter is fixed, specify it in the project config.

If the parameter is variable, you must specify in the URL.  For example, http://localhost/appname/?arg1=value1

If you want shortcut and parameter is variable, you will need to make one yourself that is pointing to the URL rather than .EXE.  You cannot use the system generated shortcut.  

Here is some documentation to read: https://docs.appeon.com/pb2019r3/pbug/ch07s03.html#defining_an_ica_project

Hi Brian;

   FWIW: What I have done with PowerCleint Apps since PB2019R2 and now PowerServer Apps in PB2021 to address this dynamic start-up set of variables is the following:

1) Create a PB Launcher App that "launches" the real PB App(s).

2) Have the Launcher PB App grab the MS-Windows WorkStation User ID (Windows API) and App Name of the App to be launched.

3) Using the User & App, proceed to a Launcher Database that returns the start-up parameters for the PC/PS App and User in question.

4) Launch the real PC/PS App via it's URL and provide the dynamic start-up parameters as required in the starting URL (as Armeen has mentioned).

5) To accomplish #4, use PB's INET Object Class and the HyperLinkToURL command to launch the App (as Armeen has mentioned).

6) To change the Start-Up parameters for any App - just update the "Launcher" DB for each App / User affected as required.

Food for thought.  ;-)

HTH

Regards ... Chris

Hi Brian;

  If you do not want to use the URL approach, you can use the App's short-cut. For example:

Hard Coded Argument (Project Painter)

Dynamic Argument

Run the Deployed App via it's shortcut value and then add any "dynamic" arguments under program control.

For example:

    C:\Users\Chris\AppData\Roaming\PBApps\Applications\localhost_OrderEntry_32_PC\OrderEntry_32_PC.exe Name=Chris

PowerClient App Runtime Result

HTH

Regards ... Chris

>>Run the Deployed App via it's shortcut value and then add any "dynamic" arguments under program control.

What do you mean by "under program control"?  

When I run this way, it is not working yet. 

C:\Users\Brian\AppData\Roaming\PBApps\Applications\localhost_test_application\test_application.exe test2

I must be missing something yet.

Thanks,

Brian

We were running build PB2019R3 2670.  

I updated this morning to R3 2728 and it appears to be working properly now.

The only side-effect is that if we change parameters, it seems to remember the old parameters.  

Ex.

Run C:\Users\user_name\AppData\Roaming\PBApps\Applications\localhost_app\app.exe "parm1 parm2 parm3" - system will launch with parm 1 parm2 parm3

We then update parameters on command line:
C:\Users\user_name\AppData\Roaming\PBApps\Applications\localhost_app\app.exe parm1

Application is still recognizing parm1 parm2 parm3.  Not sure if this is a bug or I am just not understanding of how this should work.  

Thanks again for your suggestion, we are getting closer.

Thanks,

Brian

Hi Brian;

  I just tested changing the dynamic variables and values therein and no issues ...

The App always starts with the latest assigned variables and values. Not sure why yours is not.  :-)

Regards ... Chris

Hi,

Allow me a contribution on a similar situation I've been seeing the last days. I found a way to call a secondary PowerClient application from another PowerClient application.
It works perfectly on my PC, even sending an argument (eg Company).

I don't use static arguments defined in "Run options" - "Commandline arguments".

From the open event of the application object I read the "commandline" argument.

What do you think of this way to call the application when it is already installed?, Would it be good practice to do it that way?