Tag Info

Hot answers tagged

5

CSOM and REST was introduced in SP 2010 so you wont be able to use that with 2007. SOM is an option but requires that your code runs on the servers of each farm. SharePoint Web Services will be your best option if you need to support all three versions with the same code from client computers. Lists Web Service (/_vti_bin/Lists.asmx) for getting libraries ...


3

CSOM: will work in SP online, SP 2010, 2013 and most probably 2016 REST: will work in SP online, SP 2010, 2013 and most probably 2016 OOTB Web service: will work in SP 2007, 2010, 2013 but maybe not in 2016 (and maybe not with future versions of SP online) Creating your own Web service with SOM: will work in SP 2007, 2010, 2013 and 2016


2

Method 1: Go to Central administration > Manage service applications > Search service application > Crawl rules . Use the belwo configuration and create a crawl rule. Path = ://*/AllItems.aspx Crawl configuration = Exclude all items in this path (check “Exclude complex URLs (URLs that contain question marks – ?)”) Specify authentication = Use the ...


2

You would use Get-SPLogLevel -Identity <value>, e.g. Get-SPLogLevel -Identity Database to show the current level for the Database category. You can also exclude the Identity parameter to get all categories.


2

If you're going to develop a custom following feature, you don't have to use MySite. You can have a database outside of SharePoint databases which isn't governed by ConfigDB. I guess you have good reasons to do so. The users MySite isn't created when the user signs in to SharePoint for the first time. It's created when the user clicks her name and when she ...


1

The client object model was created in 2010. CSOM did not exist in 2007. So I would recommend the server object model.


1

You may check the SPListItem.Workflows property on a given list item (e.g. the current list item) (see https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splistitem.workflows.aspx). That would give you the list of WF instances running in the scope of that item.


1

Add these scripts to your masterpage: <script type="text/javascript" src="/_layouts/sp.core.js"></script> <script type="text/javascript" src="/_layouts/sp.runtime.js"></script> <script type="text/javascript" src="/_layouts/sp.js"></script>


1

I had that same issue. Certificate turned up when I used this: foreach (var certificate in store.Certificates) { if (certificate.SerialNumber.ToLower().Equals(ClientSigningCertificateSerialNumber)) { storedCert = certificate; break; } }


1

The follow function needs the MySite Site Collection. The information is stored in the site collection. There is a special List named Social in every MySite storing this information. For the Followed Document are store under the url: https://mysite.host/personal/<name>/Social/Followed Document


1

Use SPServices for this. You can pass the lastname / first name and get the user object using which you can fetch user properties. See: http://spservices.codeplex.com/wikipage?title=SearchPrincipals


1

I'm sorry but the setup user/farm user has to be a domain account. You can find more information about this following this link Setup user account - Domain user account Server farm account - Domain user account


1

If your lists are in site collections which are within the same farm (or server), you can try this: Function Copy-SPView([string]$WebURL, [string]$SourceList, [string]$SourceView, [string]$TargetURL, [string]$DestList ) { Write-Host "Loading Sytem Modules"; #Get-Module -listAvailable | import-module if ( (Get-PSSnapin -Name ...


1

I'm not sure that I fully understand the question (and I don't have enough rep to comment), but it sounds like you could add ?Source=http://URLHERE.com to the end of your URL to redirect. If you already have another parameter set, you'll have to change it to &Source=http://URLHERE.com.


1

You can try: function openModall(pUrl) { SP.UI.ModalDialog.showModalDialog( { url: pUrl, dialogReturnValueCallback: CloseCallback } ); } function CloseCallback(result, returnValue) { if (result == SP.UI.DialogResult.OK) { // some code } else if (result == SP.UI.DialogResult.cancel) { // ...


1

Their are two ways to check this. You can Use the powershell commands [Get-SPLogLevel][1]. This example displays throttle levels for all categories. You can go to Central admin Site of farm. Central Admin> Monitoring > Configure Diagnostic logging. On this page you can expand all the categories and check th level of Log.


1

So, first off, yikes. My first question to a situation like that will always be, "Do we actually need a single library with that many things inside of it? If so, why?" Now, to the problem at hand. Why have it all in a single library? Why not create a second library and set permissions to grant read access to your read user group on that library? You ...


1

I think it would be best to have them follow a standard naming convention for the Content Type names, like VendorName(or abbrev) Document, VendorName Project, etc and use separate groups. They could then use a singular CT hub and would reduce collisions. This gives total visibility to everyone and can help with governing it too. I would fear that if it was ...


1

My issue got resolved. Actually Internal name was different for description field. After using internal name my issue got solved.


1

For me it excluding AllItems.aspx was a hit and miss. Have a look here http://practicalsharepoint2010.blogspot.com.es/2011/12/search-configuration-best-practices.html maybe it will work for you. When using this approach for some reason on the SP2010 I still had problems with crawling infoPath form libraries.


1

I don't think it is possible to get this information using APIs. This is an admin page, that uses an internal class that eventually executes dbo.proc_GetSlowestPages from the Usage and Health Data Collection Service Application database. You can try querying the database directly, but it is not a "good practice". declare @webApp uniqueidentifier select ...


1

After some intense debugging I am answering my own question. And wasted +50 StackOverflow points on this, so am an idiot. I copied and de-minified the original (global) SharePoint RenderGroupTemplate function The relevant lines: b[d+".groupHeader"]=true; a+=spMgr.RenderFieldByName(c,d,b,h); delete b[d+".groupHeader"]; Became: ...



Only top voted, non community-wiki answers of a minimum length are eligible