I have a problem with the components and the absolute links. I work with a colleague and we use the same workspace. I only enter one level down in the workspace. We don’t have a Knime Server.
The components are in a library in the workspace.
I now have the problem that when I enter a level down my links no longer work. (E: KIME workspace / BMECat MASTER)
But when I enter workspace everything works. (E: KNIME workspace)
I suspect that the workspaces will not load the Preferences. Is that so and how can i solve the problem?
the absolute Link is always based off the mountpoint (knime://LOCAL), and this gets replaced by whatever mountpoint you run your current AP with - hence I would suggest to use workflow-relative links, these should be more robust in your case (and generally more flexible). You can change the link type by right clicking the component → Component → Change Link Type…:
There you can also observe the knime://LOCAL
On another note, you have and interesting setup there - can you maybe explain your reasoning behind using a workspace within a workspace? Couldn’t you just use the same top level workspace or a workspace on the same level? Then you could also use mountpoint-relative links.
We have the case that we sometimes have to work on one thing at the same time and when we both try to go to “E: KNIME workspace” an error message comes up that the workspace is already in use and we bypass it with the lower level
would there be a better solution than ours? Or is there a possibility to use the same workspace with several users at the same time?
ah, that makes sense - no, I wouldn’t know of a better solution for collaboration (except for KNIME Server ofc ). As far as I know there is no practical solution to use the same workspace multiple times at the same time. Let’s see whether the workflow relative links work.
). As far as I know there is no practical solution to use the same workspace multiple times at the same time. Let’s see whether the workflow relative links work.