Share via

Changing Teams / OneDrive Filepaths to remove spaces and hyphens

Anonymous
2022-11-24T15:13:41+00:00

Hi

I’m trying to get a bespoke piece of software  (an ArcGIS toolbox) to read from / write to teams files / onedrive.

The first part of problem is that ArcGIS does not allow filepaths including spaces or hyphens – this is a limitation of ArcGIS that I can’t get round.

The second part of the problem is that filepaths for Teams all have spaces and hyphens in them.  I’m not sure if this is hard coded into all teams filepaths or if there’s a setting somewhere which would allow me to change this.

An example of the problem is that the toolbox will start running, but as soon as it tries to read from / write to

C:\Users\bilbys\ProjectName - ChannelName\specific_file.csv

it instead tries to work with

C:\Users\bilbys\ProjectName

i.e. cuts the filename at the first space (or possibly the hyphen, not sure), then crashes because that isn't a real file

I’ve tried creating new files a couple of different ways so the path doesn’t have spaces and hyphens in, but haven’t found a way or a setting which allows me to do this.

Does anyone know a way to do this, i.e. create something like

C:\Users\bilbys\ProjectName_ChannelName\specific_file.csv

Instead?  I know ArcGIS can handle underscores, so that would be a workable solution

Many thanks

Stephen

Microsoft Teams | Microsoft Teams for business | Files | Access OneDrive files

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2022-11-24T16:10:44+00:00

    OK - many thanks - when you say 'rename folders manually', I don't follow how I'm able to do that, as the only parts I get to name in

    C:\Users\bilbys\ProjectName - ChannelName\specific_file.csv

    are

    'ProjectName' and 'ChannelName' - the ' - ' in the middle is automatically added by Teams, and I can't find a way of removing it.

    So - for the avoidance of doubt - is what you're saying that there's a solution to my problem but that I haven't understood it, or that there isn't a solution and that's why I need to mention it to the support team?

    Many thanks for the time and explanations, much appreciated even if it's only to confirm that it can't be fixed for now.

    Stephen

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-11-24T17:39:41+00:00

    Afternoon - have tried changing onedrive name, but it gives an error message when I try to do this, presumably because it's locked to be the same as the teams one - thanks for the suggestion though - I'll investigate if there's a way of unlocking this somehow to avoid the error message

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-11-24T16:32:02+00:00

    The one I'm pertaining is for the OneDrive. Regarding Teams when you say ProjectName, are your pertaining to the Teams name?

    0 comments No comments
  4. Anonymous
    2022-11-24T15:58:15+00:00

    Hi Stephen, hope you're doing well. I’m Ian, and I’m happy to help you today.

    OneDrive can only rename files or folders with invalid characters.

    The option to automatically rename files and folders appears only for names with the following issues:

    • Names beginning or ending with a space
    • Names ending with a period
    • Names containing unsupported Unicode code points
    • Names with surrogate pair issues

    https://support.microsoft.com/office/onedrive-c...

    Unfortunately in your case, the one you mentioned are not supported. You need to rename files or folders manually in this case.

    I would suggest to submit feedback to the support engineer team so that they can add this in the future releases.

    https://feedbackportal.microsoft.com/feedback/f...

    This is a user-to-user support forum and I am a fellow user.

    I hope this helps, but please let me know if you need anything else.

    0 comments No comments