SPObject.Resolve()

Here are two cases that I face in the daily work with SharePoint which I find very common and would like to provide some technical details. 1. Hide Yes\No column If you want ho hide an Yes\No column inside content type, surprisingly you find that you can't. Or to be more specific, the SharePoint interface won't allow you to do it. I'm not sure why is that limitation but тхис is technically supported by SharePoint. Here is a JavaScript that modifies the column visibility. You just need to run it with user who have appropriate rights. var context = SP.ClientContext.get_current(); var siteContentTypes = context.get_web().get_contentTypes(); // add the GUID of you ContentType var myContentType = siteContentTypes.getById("0x010100185E5E735545B942852F513AEB77B51C"); var fieldLinks = myContentType.get_fieldLinks(); context.load(myContentType); context.load(fieldLinks); context.executeQueryAsync( function (sender, args) { var listEnumerator = fie...

This starts to be very common scenario in the SharePoint online projects: You want to have custom actions (“My Action”) that execute custom logic. The main challenge is how to load the JavaScript file with this custom logic (/sites/demo/SiteAssets/Actions/dts.demo.script.js) only when the custom action needs it. One approach described in many posts is to use a Script link.  Here is a working example: function RegisterScriptLink() { var scriptBlock = 'var headID = document.getElementsByTagName("head")[0];var newScript = document.createElement("script");newScript.type = "text/javascript";newScript.src = "' scriptBlock += '/sites/demos/SiteAssets/Actions/dts.demo.script.js' + '?ver=' + ((new Date()) * 1); scriptBlock += '";headID.appendChild(newScript);'; var context = new SP.ClientContext.get_current; this.site = context.get_web(); var collU...

The problem:  You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name." Why this is a problem? Because you need to create custom columns and content types using the default SharePoint interface. And the business users have to see properly named columns - for example "Description", not "My Description". Solution: It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):  - it supports columns with same Display Names.  - you can’t have columns with same Internal names Let’s implement the following common scenario: You are creating a SharePoint customization and you need the following column:    Type: Multiple lines of text    Internal Name: MyProjectDescription    Display Name: Description  Here is the correct way to achieve it: 1. Create the co...

The problem:  When browsing a web part page with query string parameters, the page displays an error text " Page Content field value. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ... ". This is very strang and annoying behaviour. I faced it now in SharePoint 2013 but there are blog posts explaining this error in the previous version as well. The solution I found in the posts was not to used the  reserved query string parameter .  I agree this is good option but what about the cases when something is working in SharePoint 2010 and after the upgrade to 2013 it is not. And rewriting the logic is definitely time&money consuming task. The solution I found is more simple. The solution: Download a web part page from SharePoint 2010 environment. Upload it in SharePoint 2013 library using the Explorer View. Add you web part(s) in it. Browse the page with your query string parameters and it will work cor...

Before some time I posted about an error I faced  - " Error: A duplicate field name "xxxx" was found ". This week I have the same problem. The challenge now was that the clients don't have time to rename their custom fields and deploy new code that uses the new internal names. So here is one possible approach. The problem :  Error “ A duplicate field name "Name" was found ” when a site collection feature for provisioning custom fields and content types is activated. The workaround: Edit the Name property of the problematic field(s) in the elements.xml files of the custom fields' module and custom content types' declaration. Deploy the changes with Update-SPSolution. Activate the site collection feature. Deploy the original wsp again with Update-SPSolution. Explanation:  This works because the custom fields deployed with module are not created directly in the database. They are alive through their elements.xml files. So if the origin...

I had a task to migrate the content database of a web application in SharePoint 2010 to SharePoint 2013. I performed the database-attach method (the only possible with SharePoint 2013 migration) and everything seemed to be working. The problem came when I navigated in the document libraries. There were a lot of missing files. At first, it looked scary but the reason was logical:     - I migrate the web application to a new farm with different Active Directory     - The missing files didn’t have published version so they were not missing but hidden     - Even I was logged with the System Account the security trimming hide these files The way to make the files visible is to publish them. Just navigate to   Library Settings -> Manage files which have no checked in version  . From here you can take the control over the documents and to publish them: Looks simple but it took me time to identified the issue.

Enable-SPFeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -Url http://site Because the blog is also the author's own memory, I wrote here the ID of the feature that I use very often. Why I need to activate features with powershell is because I like to develop agains Blank Site and to activate only the features that I need.