Ability to have Network based resource available through Deployment Parameter

Continuing on this idea some thoughts/questions I had on solutions that I think can serve as an option in the mean time, but which may have some caveats/uncertainty.

1. Creating a User Parameter (of type File/Folder/Url) in the workspace with the same name as the Resource Parameter of FME Flow

This is basically the idea suggested by Laura in How to use/access the parameter of an FME Flow Network Based Resource in FME Form? | Community. 

For me it seems to work great when authoring. However, I'm unsure if it will continue to work if the User Parameter is not removed before deploying to FME Flow. 

The worry I have here is if there is both;

• a User Parameter (of type File/Folder/Url) defined in the workspace.
• a Resource Parameter defined on FME Flow

which share the same name, it may be uncertain which value will be picked up in the workspace when runs in FME Flow. 

It has been a while, but I believe to remember that when I tried deploying a workspace that still contained wuch a User Parameter (of type File/Folder/Url), I believe that when I ran the workspace in FME Flow it would pick up the (default) value declared for the 'workspace parameter’, and not the value of the FME Flow 'Resource Parameter’. 

So therefore up till now I still have the habit to create the User Parameter (of type File/Folder/Url) when authoring/testing locally, and then deleting the User Parameter when deploying to FME Flow.

This has worked for me, but I think it's a bit of a hassle, and also a bit more prone to errors when forgotten/mishandled.

2. Creating a Deployment Parameter in FME Flow (using the same name as the FME Flow Resource Parameter?)

I think this can be another option. In FME Flow 2025.2 I see it's even possible to create a Deployment Parameter with the same name as the FME Flow Resource Parameter.

Potentially doing so can be a direct option for the idea posted. However, having two distinct types of parameters (Deployment Parameter and Resource Parameter) with the same name 'feels a bit iffy’ to me. 

Also I see that currently only specific types can be chosen when creating a deployment parameter in FME Flow; Text, Password, Database Connection or Web Connection.

For a (Network based) resource parameter a type analogous to the User Parameter type 'File/Folder/Url’ appears to be more fitting.

Of course one could just choose a deployment parameter of type Text, and for the value specify the same value as for the 'Directory of a network file based resource’ of the Resource Parameter, e.g. something like ‘\\SharedFolder\MyData’

I'm assuming that will probably work well. I'm just a bit worried that there may be scenario's where FME may not correctly handle/treat a Network path declared through a Deployment parameter of type text. 

Maybe I'm overthinking things, if so feel free to let me know, but I'm thinking that this may cause problems at things like automatically enclosing paths in double quotes (at least in windows), when the path contains spaces.

Lastly, if a Deployment parameter of type Text would be fine for this purpose, but having both a Resource and a Deployment parameter of the same name is not, it may be as simple as just creating the deployment parameter with an alternative name.

The small drawback here would be that you would end up with two parameters with a different name, that you may want to use for the same purpose. That may be a bit confusing.