What I would do is put the connectionfiles in a folder. Use the "Directory and filepath names"-reader to output the list to a csv. Then you can import all the items in the parameter.
hope this helps
Thanks @stalknecht. But what I'm looking for is something a bit more dynamic. The workflows I am working on are meant to be shared amongst a group of users, and there is a high likelyhood that people will name their connections differently than what is in a static list.
With the FeatureReader transformer, it presents a list of both SDE Connections and Versions to the user through the Parameters button. Is there not a way to tap into those lists and attach them to a paramater somehow??
Thanks @stalknecht. But what I'm looking for is something a bit more dynamic. The workflows I am working on are meant to be shared amongst a group of users, and there is a high likelyhood that people will name their connections differently than what is in a static list.
With the FeatureReader transformer, it presents a list of both SDE Connections and Versions to the user through the Parameters button. Is there not a way to tap into those lists and attach them to a paramater somehow??
I think you need a workspacerunner because parameters are evaluated before the translation or maybe a scripted parameter.