update-PWFolderSecurity not found.

I will try the 64 bit angle...the hyphen; there or not, gave me the same error... Thanks!

ok, I uninstalled the x86 and set up the 64 bit....same error (with Hyphen)

PS C:\PS> Update‐pwfolderSecurity

Update‐pwfolderSecurity : The term 'Update‐pwfolderSecurity' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ Update‐pwfolderSecurity
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Update‐pwfolderSecurity:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\PS> get-help pwfoldersecurity
Security Protocol now set to TLS 1.2
PWPS_DAB Version is 2.0.6.0
This is a 64-bit process.

Name Category Module Synopsis
---- -------- ------ --------

Update-PWFolderSecurity Cmdlet pwps_dab UpdatePWFolderSecurity is used to add user(s), group(s), or userlist(s) access control to specified folders.

I am told that there is a "dash", an "Mdash" and an "Ndash"...

and that the M and N dashes are placed in the text, but if the text is <space> "dash" <space> the "dash" is converted to a normal dash...

we have run into this with file and attribute names that don't like the M and N dashes.

it's pretty confusing...but now I know what to look for...

:-D  and I'm not likely to forget.... painful lessons are like that...

Bob

I almost never rely on positional. I prefer specifying the parameters. Makes everything obvious. Well, unless I'm doing something adhoc.  Anyways, I wrote that cmdlet, so, everything should work with or without specifying the parameters. Not sure why you are encountering so many issues with it.  Take a look at the examples provided.

hahaha! 

It's the "Dash" again  !!!

Get-PWFolders -FolderID $folderID -JustOne -Slow | Update-PWFolderSecurity ‐MemberType 'ul' ‐MemberName 'MediaWiki' -MemberAccess "fr,fw" -IncludeInheritance -Verbose

notice the "dash" in front of the "MemberName" is smaller...shows on the command line as a different color

So.

I copy the Example line to make sure the syntax I start with is correct...this particular text...has those other dashes

Problem solved.

Thank you for your help Guys...that's a new one for me!

Bob

Be sure you are not copying and pasting from Word or another application like that. For some reason the dashes are different.

to be sure...I will be "on guard" :-D

Thanks again, Brian!!

B

to be sure...I will be "on guard" :-D

Thanks again, Brian!!

B

I see this when copying pasting from Outlook all the time. Also issues with smart quotes. In fact I've seen this so much I wrote a little function that fixes it for me. It converts smart double quotes to dumb double quotes, smart single quotes to dumb single quotes and both endash and emdash to a normal dash.

I put it in my profile.ps1 so it's always loaded (I also set an alias cc so i don't have to type that long name i came up with)

# Convert some annoying unicode characters into normal versions
function Convert-ClipboardUnicodeEntities {
	$clip = Get-Clipboard -Format Text -Raw -TextFormatType UnicodeText
	if (-not [string]::IsNullOrEmpty($clip)) {
		# replace unicode smart open double quotes with dumb straight double quotes
		$clip=$clip.Replace([char]0x201c,[char]0x0022)
		# replace unicode smart close double quotes with dumb straight double quotes
		$clip=$clip.Replace([char]0x201d,[char]0x0022)
		# replace unicode smart open single quote with dumb straight single quote
		$clip=$clip.Replace([char]0x2018,[char]0x0027)
		# replace unicode smart close single quote with dumb straight single quote
		$clip=$clip.Replace([char]0x2019,[char]0x0027)
		# replace endash with a dash
		$clip=$clip.Replace([char]0x2013,[char]0x002D)
		# replace emdash with a dash
		$clip=$clip.Replace([char]0x2014,[char]0x002D)
		Set-Clipboard -Value $Clip
	}
}

BTW, if you're interested here's a variation on that will convert a projectwise url string that uses html/url entities and turns them into normal strings. I use this copying urls from Outlook that I want to paste into PW Explorer.

# Convert HTML & URL entities to string characters
function Convert-ClipboardHtmlUrlEntities {
	$clip = Get-Clipboard -Format Text -Raw -TextFormatType Text
	if (-not [string]::IsNullOrEmpty($clip)) {
		# URLs can have some weirdly encoded characters, let's fix those
		# clean up URL characters like %20
		$clip=[System.Net.WebUtility]::URLDecode($clip)
		# clean up html entities like <
		$clip=[System.Net.WebUtility]::HTMLDecode($clip)
		# replace &space; with a space (this is not a standard html entity, but ProjectWise uses it)
		$clip=$clip.Replace("&space;"," ")
		Set-Clipboard -Value $Clip
	}
}

That's good stuff, I'm going to grab these...

this is the first time I have run into these dashes...but I guarantee I won't be forgetting this lesson anytime soon! :-D

Thanks for the script; I will add it into my profile as well!

the HTML conversion for links into normal strings I ran into a couple weeks ago...but in Excel. So this looks like a pretty interesting solution in PWRShell.

They haven't come up often for me, but they are "sticky" when they do!

I appreciate the help, Thanks Kevin!!

Bob