Skip to main content

One of the properties of the Web Part has an incorrect format

I was trying to insert a Content Editor Web Part (CEWP) to a Master Page. I used the recommended route of using Design Manager. Let me share the steps if you are new to this:

1. Navigate to Site Settings
2. Under Look and Feel, click on Design Manager
3. Click on Edit Master Pages and click on perticular Master Page which you would like to edit (before editing, ensure you have a copy of the file for backup)
4. Click on Snippets
5. In the Snippet Gallery, insert CEWP, and set the web part properties
6. Click on Update button
7. Copy the HTML snippet generated and paste it in the Master page (.html file)
8. Upload the [[Master Page]].html file and publish

With this approach, you can attach any custom HTML/JavaScript which you would want to execute in all the pages in a site. After publishing the master page, when I refreshed the page, I got the below error:
One of the properties of the Web Part has an incorrect format. Microsoft SharePoint Foundation cannot deserialize the Web Part. Check the format of the properties and try again.

This error was frustating as it did not tell which property has incorrect format. Luckily I had the Developer Dashboard which came handy in this case. This tool gave me enough information like this:

System.InvalidOperationException: Instance validation error: 'None' is not a valid value for FrameType. at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderContentEditorWebPart.Read7_FrameType(String s) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderContentEditorWebPart.Read12_ContentEditorWebPart(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderContentEditorWebPart.Read13_WebPart()

The culprit was the property "FrameType" which was present in the HTML as


I had set this property to None in web part properties box. Interestingly, this value is not recognized by the SharePoint! Though I could have spent time in finding out the correct value, I just went ahead and deleted this property from the HTML snippet in the master page.

Well, the story did not end here. I got similar error for the following Properties one by one (It is so frustating that I had to remove each line one by one, publish the Master Page for every error).

System.InvalidOperationException: Instance validation error: 'Normal' is not a valid value for FrameState.

System.InvalidOperationException: Instance validation error: 'Modeless' is not a valid value for WebPartHelpMode.

System.InvalidOperationException: Instance validation error: 'Default' is not a valid value for Direction.

After clearing the above HTML lines, finally the page was loaded.

I am still clueless why Snippets generated the HTML code which does not work! If I get time to research on this, will share my findings here.


  1. That was helpful...
    Just to clarify - HTML code (which actually is rather XML than HTML in this case) is generated well. Whole mess happens when you upload your masterpage and it's translated to .master file. All properties are then broken into seperate lines with nice line indents so they are easy to read. But unfortunately serializer treats those whitespaces as parts of value. And there we go.

  2. Is there any solution for properties not being broken into separate lines when translated into .master file? I tried the solution provided in this blog but it breaks the styles and messes up the menu webpart.


Post a Comment

Popular posts from this blog

How to get SharePoint List or Library GUID via REST

Sometimes, you would need List or Library GUID to use that in some operation. In such cases, how do you get hold of GUID using REST API? There is a straight-forward end point which you can use: /_api/web/lists/getByTitle('ListTitle')/Id This will return the GUID of a List or Library. There is also another approach. However this approach works only if a List or Library contains at least one item. /_api/web/lists/getByTitle('ListTitle')/items This is a familiar end point which we use to fetch items of a List or Library. To get the GUID from the response, you would do: var listIDTemp =[0]; var listID = listIDTemp.substring(listIDTemp.lastIndexOf("guid") + 5).split('\'')[0]; As you can see, we are doing string operations to fetch GUID from This contains information only if the response has at least one item.

Get User Id using REST or JavaScript Object Model

Sometimes you would need to fetch the User Id based on either Login name or Email id. You would need User Id if you need to assign a user object to a people picker control or People/Group field. How do we get the Id based on Email or Login Name in client side development? We can achieve that using JavaScript Object Model or REST API. Let me share the first example using JavaScript Object Model (JSOM). var context = new SP.ClientContext.get_current(); this.user = context.get_web().ensureUser(loginName or Email); var o = { d: d, user: this.user }; context.load(this.user); context.executeQueryAsync(     Function.createDelegate(o, ensureUserSuccess),     Function.createDelegate(o, Fail) ); The above code fetches User Id for a given Login Name or Email Id. Interestingly, there is no equivalent endpoint available in REST! The Microsoft documentation talk about a endpoint but I could not get it working. So what is the way to get User Id using REST? You have to use the hidd

All about SharePoint List View Styles

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post. Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style. When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style. List of View Styles I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one. Default: This view, as name suggest, is the default style in a view. This is one of the widely seen style