Central & Local file - synchronisation!!

[dn_setshogoe]

Dear Autodesk,

(BACKGROUND STORY:)

I recently copied and pasted a local file from my desktop drive to my portable flash drive. 

The local file I copied was renamed. As I opened the copied and renamed file from my flash drive on

another desktop, it reported that the file could not be linked to its central file obviously as

the file was not opened on the same server as the central.

I continued to detach the copied an renamed local file, and chose to keep the option to later save it

as a central file with the same worksets as the original local and central file.

I worked on the copied and renamed file; saving at regular intervals. However I do see that it behaves like a central file 

in the sense that it gives me the option to make a new local when I open it indirectly from Revit. 

MY QUESTION!:

Bearing in mind that I am the only user who had been using my original local file

(connected to the central on the server  - which means nobody had updated the central from their local file),

is it possible to replace the original local file with the one I had SAVED AND RENAMED on my flash drive

by means of RENAMING IT BACK TO ITS ORIGINAL LOCAL NAME

(while its still on my flash drive) then COPYING AND PASTING and therefore overriding

the original local file?

Please could you kindly confirm if you could assist me on this as it is important to verify before

I allow other people to work on their local files

With kind regards,

Dirang.

[nathan.chapman]

The local file can be moved and renamed and it will keep its tie to the central.  Once its detached it looses this relationship.  As far as a best practice i wouldn't allow my department to use this workflow but not saying you couldn't.  My fear would be multiple people are on a project all moving their local files.  All do hours of work and come back the next day to try to put all the changes back into the central.  1 being Revit has not liked when there is so many differences from central and local.  Basically it will tell you it cant sync.  Now you have to determine who is going to lose work as someones local will be made into the central.  2 being not everyone will remember the workflow and at some point detach the model and then try to put changes back into the central.  That person will then have to lose there updates are spend the time on copy/paste into central.  So i would say try no to use this workflow.

Nate

[RDAOU]

@dn_setshogoe

1. No one besides you have been syncing to central since when? In other words When was the last time other users synced?
2. after you moved the copied local to your laptop, have you been working on the desktop and syncing?
3. Have others not worked on their locals or they just haven't been syncing

No hard feelings but your workflow is a mess... If your laptop version is the up to date one and no one (since you started working on the laptop version) has worked and synced to the original central, why don't you just create a new central from you laptop's and recreate locals for all users? I don't see the point in replacing your desktop local with that of the laptop to then try update the old central!