Best practices for uploading and linking files

[ycymry]

We have an FTP site that we use to post our revit models for our consultants to download, and vice versa. I have always thought that creating a "detached from central" file copy of the model first, then uploading it to the FTP, would eliminate any link between that file and our central file, but it seems our consultants, in order to use or link the file once they have downloaded it, find that they need to detach again, or the file "looks" for and can't "find" our central file (which is not on the FTP, but a different server).

Is there a better way to do this? Are we missing a step, here?

[cliff collins]

Detaching from Central is the correct method., Then in addition to that, also go into Manage Links and detach/remove the linked files.

It could be that the Consultants file which they download may still be trying to find a path to your linked models?

Hope that helps.

cheers

[wmullett]

Sounds like your consultant's need some help - not really you.

Anytime you detach from central then save the file, it becomes a new central That is what you saved to FTP and that is correct. If they then open that file without being detached, it will now be a local looking for a central. They can do that but they should be doing a save as to make a new central on their own network. Or they can just copy the FTP files to their network.

In most cases, they really don't even need to be opening your file anyway. They only need to link it. The tricky part comes if you have linked files that they also need. If all of those are relative pathed and those files were copied over into the correct folder, they should not have any problems.

[Steve_Stafford]

As has been written but I think deserves stating yet another way:

The file you upload, and they then download, is a local file as soon as they download it as far as Revit is concerned. When they park the downloaded file on their server it is in a new location (triggering the local file status).

When they link this file to their project Revit will consider it a local file that is referencing an inaccessible central file. For this reason Autodesk recommends only linking to central files. The newly downloaded file should be opened with Detach from Central and then Saved to create a new central file on their own server (severs the relationship that it had with your version on your server). Alternatively they can choose to Open the file and use Save As to create a new central file. I think DFC is the better way.

Hopefully, if it wasn't clear enough, it is now?

[tcatana]

I have a similar situation, where I downloaded a project with more than a dozen files that are linked together in various ways. They are all central files and I had to open and save to central on all of them until all the errors went away, then I got the pleasure of reloading all the links.

I think there should be a better link methodology. even with all the files in one location, it could not find the files and was looking for a file structure from the consultant I received the files from. So word of warning - Keep your folder structure simple and make sure you do not save specific paths if you are planning on sharing files.

[ycymry]

As has been written but I think deserves stating yet another way:

The file you upload, and they then download, is a local file as soon as they download it as far as Revit is concerned. When they park the downloaded file on their server it is in a new location (triggering the local file status).

When they link this file to their project Revit will consider it a local file that is referencing an inaccessible central file. For this reason Autodesk recommends only linking to central files. The newly downloaded file should be opened with Detach from Central and then Saved to create a new central file on their own server (severs the relationship that it had with your version on your server). Alternatively they can choose to Open the file and use Save As to create a new central file. I think DFC is the better way.

Hopefully, if it wasn't clear enough, it is now?

now I get it........ somehow, I (and they) missed the whole fact that detaching from central creates a NEW CENTRAL file, and therefore their downloaded and parked in their server file is looking for the cnetral file located on the FTP. It all comes clear.

Thanks, all, for your responses!

[cliff collins]

We have been having major issues with using FTP as a way to collaborate with large, complex Revit projects, with offices located across the USA. Over 400 MB of linked models, Arch, ID, S, MEP, etc.

We are investigating several alternative methods:

1. WAN / accelleration; MPLS or VPN

2. Web-based collaboration site.

3. "The Cloud"---not quite there yet, but coming soon.....ala Little Diversified method

4. Google Apps

Anyone have some experience/recommendations?

[rkitect]

In my experience and honest opinion, best practice for inter-office consultant file linking remains Riverbed's Steelhead (http://www.riverbed.com/products/appliances/) server hardware/software solutions. I've been on a project with live central file linking with a team in India with this technology with no problems.(which I believe falls under cliff's #1 listed above). Of course the drawback is that both ends require hardware in order for it to work. They have recently (a few years back?) released a software solution that interfaces with the hardware product, but I have no experience with that.


Google Apps, hmm haven't even considered that. Interesting idea :)

[twiceroadsfool]

We're having great success with both WAN acceleration and Remote desktop for the gents in the field (on actual sites).

Both are great. But since i dont drink Kool-aid ill keep my recommendations to myself. :)

[cliff collins]

Here's another one pointed out by Steve Stafford:

http://www.cuteftp.com/wafs/index.aspx

cheers

[davidcobi]

We have an FTP site that we use to post our revit models for our consultants to download, and vice versa. I have always thought that creating a "detached from central" file copy of the model first, then uploading it to the FTP, would eliminate any link between that file and our central file, but it seems our consultants, in order to use or link the file once they have downloaded it, find that they need to detach again, or the file "looks" for and can't "find" our central file (which is not on the FTP, but a different server).

Is there a better way to do this? Are we missing a step, here?

Old thread but I think this still applies.

I would E-transmit before sending a model to anyone.
And I always "de-claw" before opening a received model for the first time.
(detach and close all worksets)

I de-claw when I upgrade models too.