Hi @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.
Hi @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.
That worked, thank you!
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
That worked, thank you!
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
Alas, my solution did not always work. When you set the path from an attribute in WorkspaceRunner you loose the ability to set the Workspace Parameters. So Xiaomengs solution is the one that works if you need that functionality.