Enable Internal Name in Create Column page

Shantha Kumar — Sun, 07 Feb 2010 03:38:58 +0000

In SharePoint out-of-Box, we can’t able to add the internal name for the SharePoint field i.e., Columns. But we can enable that by modifying the Create column page on 12 Hive.

For that we have to modify the FldNew.aspx page, that is available under 12 Hive\TEMPLATE\LAYOUTS folder.

Before modifying, take a copy of that file.

Step 1: Open the file and search for this line,

name="Name">

Step 2: Replace the above line with the following codes,

                            name="Name" MaxLength=255 size="’ EncodeMethod=’HtmlEncode’/>" />

Step 3: Now the page is enable with the internal name. Now we can enter the different name for Internal name and display name on creating a new column.

cheers.

How to get InternalName in ListEdit Page

Shantha Kumar — Fri, 25 Sep 2009 01:09:08 +0000

In SharePoint the column or field has two names. One is DisplayName, used to view the field name publically in all pages and another is InternalName used internally to refer the Field. This Internal name will be used in CAML Queries, during retreiving inserting and updating the list item.We can’t see this Internal name in any pages normally, but we can do some work around for getting this internalnames, such as writing the code & look in to the url of the particular field.

Now i giving a simple tip on displaying the InternalName on ListEdit page itself, this will help us in knowing internal name quickly and consume the time when we work up on List and ListItems.

For that, we have to edit the ListEdit.aspx page, which is available under :\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\
Before going to edit that page, backup that file and open it. This is the screenshot, taken before editing the page,
In the ListEdit page, add the Column as InternalName under Columns section,To add the header for Internalname under Columns section, Search for the following line
for (Int32 iIndex = 0; iIndex < spFields.Count; iIndex ++ )
At first we have to add the header column, for that before the above searched line there is tag with three header tags, add the following within the tag,Internal NameAfter adding the line, the code look like this,

” EncodeMethod=’HtmlEncode’/>

” EncodeMethod=’HtmlEncode’/>

<% if (!spList.ContentTypesEnabled) { %>
” EncodeMethod=’HtmlEncode’/>
<% } else { %>
” EncodeMethod=’HtmlEncode’/>
<% } %>

Internal Name

for (Int32 iIndex = 0; iIndex < spFields.Count; iIndex ++ )
And then we have to add the InternalName for each field type, for that
Search for the following if condition line,

if (spField.ReadOnlyField && !bCountRelated)

The above line checks the current field is read only or not, by default the read only fields are User and Calculated Columns
If you look in to the page, you can able to see the switch case statement under the if condition. Switch case statement checks the each read-only field type and adding the row contents such as (Display name, field type and Require or not) columns based on the field type,so we have to add the following line (column) within each case statement,
<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

In this page, spField.InternalName displays the Internal Name for the current field type.

The above TD tag content ensures that, the each field row has its own Internalname
The else condition refers to the non-read only fields, If we add this line <%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>, the internal Name will be appeared on all the non-read only field types.

After adding all the lines, the code for the if and else condition will be look like this,

if (spField.ReadOnlyField && !bCountRelated)
{
switch (spField.Type)
{
case SPFieldType.Calculated:
rowClass = (rowClass == “”)? “ms-alternating” : “”;
%>

” HREF=”FldEdit.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(”B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>”> <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>

” EncodeMethod=’HtmlEncode’/>

<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
break;
case SPFieldType.User:
rowClass = (rowClass == “”)? “ms-alternating” : “”;
%>

” HREF=”FldEditEx.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(”B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>” > <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>

<%SPHttpUtility.HtmlEncode(spField.TypeDisplayName, Response.Output);%>

<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
break;
default:
if (spField.XPath != null && !spField.Hidden)
{
%>

<%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>

<%SPHttpUtility.HtmlEncode(spField.TypeDisplayName, Response.Output);%>

<% if ( !spList.ContentTypesEnabled && spField.Required == true ) { %> <% ; } %>
<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
}
break;
}
}
else
{
rowClass = (rowClass == “”)? “ms-alternating” : “”;
%>

<%if (Enum.IsDefined(typeof(SPFieldType), spField.TypeAsString) && spField.Type != SPFieldType.Lookup && spField.Type != SPFieldType.User) {%>
” HREF=”FldEdit.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(”B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>”> <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>
<%} else {%>
” HREF=”FldEditEx.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(”B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>”> <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>
<%}%>

<%SPHttpUtility.HtmlEncode(spField.TypeDisplayName, Response.Output);%>
colspan=2
class=ms-vb2>
<% if ( !spList.ContentTypesEnabled && spField.Required == true ) { %> <% ; } %>
<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
}

The final outcome will be as follows,

To download the listedit.aspx page, click here!

Welcome to ShanthaKumar's Blog » InternalName

Enable Internal Name in Create Column page

How to get InternalName in ListEdit Page