OneDrive


Feedback by UserVoice

Chris Meacher

My feedback

  1. 2,132 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chris Meacher supported this idea  · 
  2. 3,539 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chris Meacher supported this idea  · 
    An error occurred while saving the comment
    Chris Meacher commented  · 

    I understand MS have little interest in solving this as it is "by Design", the point everyone is trying to make is this is an extremely poor design, as it severely limits usability and appears a relatively simple fix.

    For each instance of the OneDrive app:
    1) Keeping to the 256chr limit, add a string variable to be stored with each synced folder to store it's local root name

    2) On startup check if this variable is set for each synced folder, if not then set based on default rules (to existing folders - nothing can have been changed by this point)

    3) Add option in settings to rename the local sync instance

    4) Validate rename entry for
    (a) invalid entry - reject
    (b) existing sync - warning / reject
    (c) existing folder - ask if sync to contents of this folder instead (useful if had old link that broke)

    5) temp desync to unlock existing folder, rename (or link to new folder), update variable, re-establish sync

    6) bibbity-bobbity-boo

    Not only resolves issues on long tenant or folder names, but also of syncing same folder names from different locations on same site. E.g. If I wish to sync from following folders:
    -Tenant_Commercial/Projects/ProjA/AfP/Latest
    -Tenant_Commercial/Projects/ProjB/AfP/Latest
    -Tenant_Commercial/Projects/ProjC/AfP/Latest

    What I get locally is
    -Tenant_Commercial - Latest
    -Tenant_Commercial - Latest2
    -Tenant_Commercial - Latest3

    And no it's not poor structure - the ProjectA commercial lead needs to sync all of ProjA, the ProjectB lead, all of ProjB and so on, so it's set for the company requirements not my personal ones.

    This additional option would allow the users to resolve both the really long tenant/folder names issue, and the duplicated folder names issue, and give the user much more control of how things are being saved to their local device...

    An error occurred while saving the comment
    Chris Meacher commented  · 

    I work in a company on multiple projects, with a standard folder structure for each project, and need to sync the same folders from multiple projects to produce cost roll up reports. This causes an issue in OneDrive as the synced folders all have the same name, and so are indistinguishable.

    E.g.
    CompanyTenant/Projects/Project01/Commerical/AfP/
    CompanyTenant/Projects/Project02/Commerical/AfP/
    CompanyTenant/Projects/Project03/Commerical/AfP/

    Syncs to:
    CompanyTenant-AfP
    CompanyTenant-AfP(1)
    CompanyTenant-AfP(2)

    I would like to rename the local folder to something meaningful and keep the sync working, but unable to due to OneDrive restrictions.

    Please note: This is different to the renaming of the root folder issue, which I also agree with and have voted for under the most popular post (over 1,000 votes) here:
    https://onedrive.uservoice.com/forums/913522-onedrive-on-windows/suggestions/8729746-allow-onedrive-for-business-folder-to-be-renamed

  3. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chris Meacher supported this idea  · 
  4. 652 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chris Meacher supported this idea  · 

Feedback and Knowledge Base