And then build a path to a file that is always on the KNIME server by adding a blue connection to such a node
I sometimes find the path and file handling not that intuitive but it should work. You have to always think about what your environment is and what paths the workflow can see at the moment.
This might also serve as an example
I do not have access to our KNIME server at the moment so I cannot build a full example.
@mlauber71 thanks for your answer. This works in case of the csv reader, but not with the file chooser widget, because I have to select a file via “Browse” in the file choose widget and this selects an absolute path.
Furthermore I can’t give this path to the model reader node via a flow variable, because the new Model reader node (from the last update) doesn’t let me use that flow variable from the file chooser widget.
You could try and execute the workflow on the server a a new process and see what kind of selection it would run. Maybe you could also try this via the web interface.
Is there no chance that you could configure the position of the model? So you would not have to manually select it?