A parameter value is something you typically set before you run your workspace. These are the base parameters.
If you need a value that is dynamic set, you should store it in a variable and get it from there. You could use a AttribureCreator, a FeatureJoiner/FeatureMerger or a VariableRetriever and VariableSetter. (make sure the Setter is done before the Retriever is started).
If you really want to set the parameter, what I don't think you need, you could get the variable and start a WorkspaceRunner with that parameter set. In this case it would be a public parameter I guess.
A parameter value is something you typically set before you run your workspace. These are the base parameters.
If you need a value that is dynamic set, you should store it in a variable and get it from there. You could use a AttribureCreator, a FeatureJoiner/FeatureMerger or a VariableRetriever and VariableSetter. (make sure the Setter is done before the Retriever is started).
If you really want to set the parameter, what I don't think you need, you could get the variable and start a WorkspaceRunner with that parameter set. In this case it would be a public parameter I guess.
Thanks @jkr_da I was able to accomplish this with the featuremerger. I guess my original question was geared more towards running a series of SQLCreators based off of Parameter values enclosed in the where clause. Basically to limit the amount of records being read to speed up the workspace. However your answer solved my issue! Thanks!!