Skip to main content

Creating New List Form in Discussion List? Be aware of limitations!

If you add a New Form to the Discussion List and set it as default, you would expect all Discussion List web parts to point to the new form. Unfortunately, it does not! To explain this behavior, let me start with a custom List.

Let us take any custom List. By default, it has 3 forms (New, Edit, and Display). Open SharePoint Designer, navigate to this List and add a new "New Form" (call it NewForm2.aspx) and make it as default.

Now wherever you have added the above custom List as a web part (List View Web Part), when you click on "new item", it opens up the newly created NewForm2.aspx. This is what we would also expect since we have made it as default New Form. If you closely observe the hyperlink of "new item" in a List View Web Part, it looks as below:


Basically when we click on "new item" link, it takes us to a layout page listform.aspx with ListGUID and other parameters and finally NewForm2.aspx is loaded. May be internally this is handled.

Unfortunately this behavior is quite different when it comes to a Discussion List. If you create a new "New Form" and make it as default, none of the Discussion List web parts point to newly created form. If you closely observe the hyperlink of "new discussion" link of the web part, it points to:


This does not point to listform.aspx, instead it points to NewForm.aspx. Now, when you change the default to NewForm2.aspx, the web part still points to NewForm.aspx only. That means, if at all you want to create a new "New Form" and set it as default, you also need to change the hyperlinks of all the web parts of Discussion List. That is really a cumbersome job if you have many web parts in place. If you are using Community site, additionally you need to change in Category.aspx page as well!

Having understood the problem, let us look at a simple solution to this.

Approach 1: This approach is for people who are not familiar with JavaScript.

Open Developer Tools (F12 in IE), navigate to the page where Discussion web part is added and then focus DOM Explorer to the "new discussion" hyperlink. Copy the entire code within the DIV with class "ms-comm-heroLinkContainer".

Edit the page and insert Content Editor Web Part and add the above HTML code. Ensure that you replace NewForm.aspx to the newly created form name (in my example, NewForm2.aspx). Save the Content Editor Web Part.

With this a new link is displayed which points to NewForm2.aspx. Now we need to hide the link of the existing web part. Select Discussion List View Web Part and Edit its properties. Change the Toolbar property from "Full Toolbar" to "No Toolbar", click OK. Save the Page.

Approach 2: This approach is for people who are familiar with JavaScript.

Edit the page and insert Content Editor Web Part and add the below code within Script HTML tags:

$(document).ready(function () {

    var hrefVal = $(".ms-comm-heroLinkContainer a").attr('href');

    hrefVal = hrefVal.replace("NewForm.aspx","NewForm2.aspx");

    $(".ms-comm-heroLinkContainer a").attr('href',hrefVal);


With a simple script/HTML, we can make the web part "new item" link to point to the new form.


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