I created a backup script that compresses and encrypts individual files. The destination is a OneDrive synched folder. The files copy OK - and most synch. However, some files have characters in their name that are legal with Windows, but not when saved to OneDrive (for example, '#' - which is very common with some of our user's naming conventions).
I know that I can solve by compressing to a single file where I specify the name. However, the file will be so large that we will be forever synching when there are only a few changes per unit of time that really need updating.
Is there a way to specify file names to adjust to rules of the destination server? Perhaps the illegal characters from one device could be mapped into something else when moved to the other?
Thank you for your help ...
Before posting, and to avoid disappointment, please read the following:
- This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
- If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.
- If you are entitled to technical support then please submit a support ticket. Please do not post the same question to the forum and also via a support ticket. Once again, 2BrightSparks does not provide technical support via this forum.
Onedrive File Naming Conventions
-
Swapna
- 2BrightSparks Staff
- Posts: 1003
- Joined: Mon Apr 13, 2015 6:22 am
Re: Onedrive File Naming Conventions
Hi,
Sorry, but this feature is not supported with cloud services (it is only supported with FTP). However, I will pass your request to the relevant department for further review.
Thank you.
Sorry, but this feature is not supported with cloud services (it is only supported with FTP). However, I will pass your request to the relevant department for further review.
Thank you.
-
gogogadgetscott
- Newbie
- Posts: 2
- Joined: Wed Oct 25, 2017 5:45 pm
Re: Onedrive File Naming Conventions
Is this not the point of Expert Mode: Cloud, Advanced - Automatically translate invalid filenames?
That said, I too am having trouble with pound sign in filenames with both Onedrive and SharePoint. Even with Automatically translate invalid filenames enabled I get error "Failed to copy from Local : invalidRequest: The request is malformed or incorrect." with filenames containing pound sign. Please add pound sign to Onedrive/SharePoint translate map.
Scott
That said, I too am having trouble with pound sign in filenames with both Onedrive and SharePoint. Even with Automatically translate invalid filenames enabled I get error "Failed to copy from Local : invalidRequest: The request is malformed or incorrect." with filenames containing pound sign. Please add pound sign to Onedrive/SharePoint translate map.
Scott