Changing absolute file paths into relative

Question

Hello!

So my company recently switched cloud storage providers which makes all of the absolute paths in my workflows incorrect. I've been changing these to relative by navigating to "Workflow Dependencies" and manually writing in the relative path name then testing them to verify I don't receive "this file directory does not exist" message. I have one workflow with A LOT of dependencies. I've been able to successfully change about 80% of the paths to relative, but for a lot of them I will change them in Workflow Dependencies, test and ensure they all work, then close the workflow dependencies pop up. After doing this the paths will revert back to absolute when I run the workflow and sure enough they are absolute when I reopen my dependencies window. Any ideas on why this might be happening? Thanks!

KGT · Accepted Answer

I haven't seen this happen, but I would look for what the difference/trend is for the ones that won't change. I just tested one on my machine with 3 dependencies. 2 were on my network drive and one on my C Drive. As the workflow was on my C Drive, the Network drive connections stayed as such after clicking "All Relative". That makes sense as the relative connection is redundant. So, the only time that they should revert back is when the ".\" reference is redundant as the fully qualified path would need to be in the reference anyhow. Such as "..\..\U:\Projects\" would stay as "U:\Projects\". I can't guess to any more without more information, but I would definitely look for similarities in the ones that don't stay converted.