+4I have a set of workspaces on a network disk that are called from a master workspace with workspace runners. But when I copy the master workspace to a different location the paths to the modules become relative to the new master. And thus the link is broken. How can I retain the absolute path?
Sincerely,
Robin Nilsson
+3Hi @karnil, I think this question is very similar to yours, and Dave's answer has a workaround that should apply to your scenario as well. In short, if you reset the Child workspace's path, after moving the parent workspace, Now the Child workspace path is no longer relative to the parent workspace, next time you move it, it should remain absolute.
+4Hi @karnil, I think this question is very similar to yours, and Dave's answer has a workaround that should apply to your scenario as well. In short, if you reset the Child workspace's path, after moving the parent workspace, Now the Child workspace path is no longer relative to the parent workspace, next time you move it, it should remain absolute.
And now I also realized that since i have so many workspace runners, it is more effective to make a published parameter containing the path to the Child-workspaces folder and just before each WorkspaceRunner create an attribute with the path to the wanted ChildWorkspace. Like in the attached image.
workspacerunnerpath.jpg
+4
And now I also realized that since i have so many workspace runners, it is more effective to make a published parameter containing the path to the Child-workspaces folder and just before each WorkspaceRunner create an attribute with the path to the wanted ChildWorkspace. Like in the attached image.
workspacerunnerpath.jpg
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
