Skip to main content

Publish Files Edited via aDrive Desktop

This article helps you understand how to publish a file edited via the aDrive Desktop application.

Updated over a week ago

After editing a file locally via aDrive Desktop, Asite users can publish the revised file as a new revision on Asite in the relevant project folder. Below are the steps to publish a file edited via the aDrive Desktop:

  1. Open the aDrive Desktop window, which contains a record of your edited file.

    • If your edited file is in a different folder on your local device, save a copy of it to the working folder as indicated in your aDrive Desktop preferences, and then refresh the aDrive Desktop window.

    There are two options when publishing files edited via aDrive Desktop - 'Upload & Finish' and 'Upload & Continue'. Below is the difference between these two options:

    'Upload & Finish' will publish the selected revision and remove the existing checkout from the file.
    'Upload & Continue' will only publish the selected revision. The existing checkout on file will remain unchanged.
    Click the 'Edit' icon to continue editing the file before publishing it as a revision. The file will open for editing in the default native application configured on your computer for the selected file format, as applicable.
    To view edited revisions on the file, click the Show revisions of the File icon.


    It will show all the revisions of files saved via the aDrive Desktop on your local device. You can click the eye icon to view each revision, based on which you can decide which one to publish. Then, as explained above, you can use either the 'Upload & Finish' or 'Upload & Continue' option to publish the corresponding file revision.

    If the file opened for editing is closed, you can always click the edit icon in the aDrive Desktop window to resume editing the corresponding file.
    ​aDrive Desktop will notify you if the file you have locally edited via aDrive Desktop has a newer version of the same file available on the Asite web application. In such a scenario, you will be prompted with options.

  2. Select an appropriate option to continue. The 'Upload' window will work based on the folder configuration of the selected project. In the case of a 'simple upload', the 'Upload' window will not appear, and the file will be directly published to the relevant project folder in Asite Cloud.

    If you're publishing with attributes, you can click here to learn how to publish a revision of an existing file (step 3 onwards). The option to distribute a file is unavailable when publishing files via aDrive Desktop, though it can always be distributed later from the Asite web application. Click here for detailed help on how to distribute a file.

  3. The aDrive Desktop app window includes a separate tab, 'Recent Uploads', where you can view a list of all files recently published via the aDrive Desktop.

    Click the 'Open in Webapp' button to view the file in the Asite web application.

    Click the 'Open & Edit' button to edit the file. The file will open for editing in the default native application configured on your computer for the selected file format, as applicable.
    ​


Automatically Delete Local Copies After Upload

  • You can configure aDrive Desktop to automatically delete locally edited file copies from your aDrive folder once they have been successfully uploaded to the Asite Cloud. This setting is disabled by default.

  • When enabled, any file that you edit and upload will be removed from your local aDrive folder after the upload is complete.

  • This preference does not apply to one-way or two-way synced folders.


Enable Automatic Deletion

  1. Open aDrive Desktop.

  2. Click the Profile icon.

  3. Select Preferences.

  4. In the Preferences panel, locate the Delete local files on upload to Asite Cloud radio button.

  5. Select Yes.

  6. Click Save.

Once enabled, edited files that are successfully uploaded to the Asite Cloud will be automatically removed from your local aDrive Desktop folder. This helps you manage local storage and avoid duplicate files.


Check: FAQs


Did this answer your question?