Trimble Connect doesn’t work that way. You don’t work directly from the cloud because Trimble Connect downloads a copy to your local hard drive. And it also saves local before uploading to the Trimble Connect servers…
If the folder structure is the same and the file names remain the same there should be no need to re-link, LayOut will see an updated file and alert you when you start LO.
I share DropBox folders (copies of my local work, near mirror images) and my clients use. They never have issues with LO.
I don’t find that to be true.
If the “check out location” is on my local drive, it has a different root drive and path than the one on Google Drive and a different root drive and path than my teammate because they are in different drives, therefore each team member has to relink the SU file path in LO every time it is checked out to reflect their root drive. (Even if the file names are the same)
In other words, the file structure changes for each check out.
Ok. It was my understanding (and what I’ve seen in practice) that if the LO and SKP are in the same folder they find each other when passing back and forth. I use DropBox.
I don’t use Google Drive so I guess this whole ‘check out’ thing breaks that.
Am I understanding that you have local copies as well as network copies and behind the scenes it keeps track of who has what open and what is most current?
Try and keep folder structure as simple as possible. If this can’t be done, there’s an option to map your drive, or dropbox or x cloud provider folder to a drive letter, on every computer accessing your shared folder, so everyone sees the same folder structure. This on Windows. Google “map network drive”