Tag Info

New answers tagged

1

Correct, only the current version impacts the LVT.


3

I asume you are filtering by site and not by library. You could do something like this: $ignoreSites = @("http://siteurl/site1", "http://siteurl/site2") Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue $siteURL = $args[0] $site = Get-SPSite($siteURL) $webs = $site.AllWebs | ? {$_.Url -notin $ignoreSites} foreach($web in $webs) { ...


1

Instead of using the Relevant Documents Web Part, you could you a List View Web Part and filter the list view for the current user. Then you could easily add/remove whatever columns you want from the list view. To do this, edit the List View Web Part properties and then under Selected View click on Edit the current view. Under the Filter section, set the ...


0

If I understand correctly, could you not just add another list view and set it as a "Personal view", edit the view in your Library settings and then add that to the Web Part or wherever you want to place it?


0

The form will still be compatible, and the digital signatures will remain in tact. (see caveat at the bottom) Why? The user's form (an .xml file) contains no references to the form template's form id, so it's none-the-wiser. The form id is used, however, for caching purposes on the local machine. Your computer will check its cached versions of the form for ...


0

Versioning on lists can also be Enabled/Disabled using PowerShell. I have used this CSOM PowerShell function to enable versioning on a custom list. Since its a CSOM you need not run this on server, i.e. you can execute this function remotely provided you have installed Client APIs Try{ Add-Type -Path 'C:\Program Files\Common Files\Microsoft Shared\Web ...



Top 50 recent answers are included