3

Migrating about 200,000 files to OneDrive for business, and discovered that there are a few characters they don't like - the biggest offender is #. I have about 3,000 files with a hash, and I'd like to replace them all with just No.. For example, old: File#3.txt new: File No.3.txt

I tried using a PowerShell script, but it doesn't like # either:

Get-ChildItem -Filter "*#*" -Recurse |
  Rename-Item -NewName { $_.name -replace '#',' No. ' }

I'm not having much luck figuring out the syntax for reserved characters - I tried \#, #\, '*#*', no luck.

Can anyone shed light on this or provide a quick method to recursively replace all of these hash tags?

Thanks.

Emperor XLII
  • 13,014
  • 11
  • 65
  • 75
Mark Sinford
  • 135
  • 1
  • 8
  • you may get more answers if you specify environment in which you are working either in tags or in title – 4rlekin Oct 30 '14 at 08:24

1 Answers1

5
Mode                LastWriteTime     Length Name       
----                -------------     ------ ----      
-a---        30.10.2014     14:58          0 file#1.txt
-a---        30.10.2014     14:58          0 file#2.txt

PowerShell uses the Backtick (`) as an escape character, and double quotes to evaluate content:

Get-ChildItem -Filter "*`#*" -Recurse |
Rename-Item -NewName {$_.name -replace '#','No.' } -Verbose

or

Get-ChildItem -Filter "*$([char]35)*" -Recurse | 
Rename-Item -NewName {$_.name -replace "$([char]35)","No." } -Verbose

Both will work.

Get-ChildItem -Filter "*`#*" -Recurse | 
           Rename-Item -NewName {$_.name -replace "`#","No." } -Verbose

VERBOSE: Performing the operation "Rename File" on target 
"Item: D:\tmp\file#1.txt Destination: D:\tmp\fileNo.1.txt".
VERBOSE: Performing the operation "Rename File" on target 
"Item: D:\tmp\file#2.txt Destination: D:\tmp\fileNo.2.txt".

This would also work,

Get-ChildItem -Filter '*#*' -Recurse |
Rename-Item -NewName {$_.name -replace '#', 'No.'} -Verbose

VERBOSE: Performing the operation "Rename File" on target 
"Item: D:\tmp\file#1.txt Destination: D:\tmp\fileNo.1.txt".
VERBOSE: Performing the operation "Rename File" on target
"Item: D:\tmp\file#2.txt Destination: D:\tmp\fileNo.2.txt".

Because the PowerShell parser is smart enough to figure out your intent.

evilSnobu
  • 24,582
  • 8
  • 41
  • 71
  • Here's a fantastic post by Jeffrey Snover if you want to dig deeper into variable expansion in strings. Http://blogs.msdn.com/b/powershell/archive/2006/07/15/variable-expansion-in-strings-and-herestrings.aspx – evilSnobu Oct 30 '14 at 20:52
  • Works perfectly... brilliant. What a difference one character can make. THANK YOU – Mark Sinford Oct 30 '14 at 21:26