Nishant Rana

Adding a Read Only Field or Read Only Column to a SharePoint List

We had a requirement to add a read only column to one of our document library. Using Create column it isn’t possible to add a read only column. One option could be to create the new column and then using SharePoint designer we can make use of JavaScript and modify the NewForm.aspx and EditForm.aspx to display that field as read only.

We thought of adding it as a Site Column making use of ReadOnly property of field.

<?xml version=“1.0“ encoding=“utf-8“?>

<Field ID=“{0B8A5574-80BF-4d5e-99B9-9A25D8E8D21E}“

Name=“_IsApproved“

DisplayName=“Is Document Approved?“

Group=“Custom Columns“

Type=“Text“

Required=“FALSE“

ReadOnly=“TRUE“

“

</Field>

</Elements>

However if we set ReadOnly as True the field doesn’t appear on Site Settings pages for managaing site columns and content types. However we can add it to the view using the below code

SPSite oSiteCollection = new SPSite(@”http://servername:port”);

using (SPWeb oWebsite = oSiteCollection.OpenWeb())

{

SPList oList = oWebsite.Lists[“ListName”];

oList.Fields.Add(“Is Document Approved?”, SPFieldType.Text, false);

oList.Update();

SPView oView = oList.DefaultView;

oView.ViewFields.Add(“Is Document Approved?”);

oView.Update();

}

However the field was still appearing in editform.aspx and newform.aspx in editable mode.

So finally tried this

Modified the definition for the custom site column as following

<?xml version=“1.0“ encoding=“utf-8“?>

<Field ID=“{0B8A5574-80BF-4d5e-99B9-9A25D8E8D21E}“

Name=“_IsApproved“

DisplayName=“Is Document Approved?“

Group=“Custom Columns“

Type=“Text“

Required=“FALSE“

ReadOnly=“FALSE“

ShowInDisplayForm=“TRUE“

ShowInEditForm=“FALSE“

ShowInNewForm=“FALSE“

</Field>

</Elements>

Setting ShowInDisplayForm and ShowInEditForm as False and keeping ReadOnly as False so that the field could appear within Site Settings pages for managing site columns.

This last solution worked ..

The feature file for installing the above site column

<?xml version=“1.0“ encoding=“utf-8“?>

<Feature Id=“D829F71B-7FCC-4f0d-950D-6B562AFF400E“

Title=“MyCustom Feature“

Description=“This is my custom column feature“

Version=“12.0.0.0“

Scope=“Site“

xmlns=“http://schemas.microsoft.com/sharepoint/“>

</ElementManifests>

</Feature>

Now the only way to edit the column was through SharePoint Object Model

SPSite oSiteCollection = new SPSite(@”http://servername:port”);

using (SPWeb oWebsite = oSiteCollection.OpenWeb())

{

SPList oList = oWebsite.Lists[“ListName”];

SPListItem item = oList.Items[0];

item[“Is Document Approved?”] = “These are my changes”;

item.Update();

}

That’s it..

Adding custom menu and button to custom entity through ISV.CONFIG

To add custom menu and button to Entity form,

Go to Customizations-Export Customizations-Select ISV.CONFIG.

Open the customizations.xml file and add the following xml tags to it

<Menu>

</Title>

</Titles>

</Title>

</Titles>

</MenuItem>

</Menu>

</CustomMenus>

</MenuBar>

</Titles>

<ToolTip

LCID=“1033“

Text=“My custom button tooltip“ />

</ToolTips>

</Button>

</ToolBar>

</Entity>

That’s it ..

Using Siebel CRM On Demand Web Services in Microsoft.NET

1) Create a new windows application.

2) Put the following code in the form load

private void Form1_Load(object sender, EventArgs e)

{

string loginUrlString = “https://servername/Services/Integration?command=login”;

String sessionID = ManageSession.Login(loginUrlString, @”orgname-devusername”, “password”);

}

3) Define the login method within ManageSession class in the following manner

public static string SessionID = “”;

public static String Login(String loginUrlString, String userName, String password)

{

try

{

// create a http request and set the headers for authentication

HttpWebRequest myRequest = (HttpWebRequest)WebRequest.Create(loginUrlString);

HttpWebResponse myResponse;

myRequest.Method = “POST”;

// passing username and password in the http header

// username format if it includes slash should be the forward slash /

myRequest.Headers[“UserName”] = userName;

myRequest.Headers[“Password”] = password;

myResponse = (HttpWebResponse)myRequest.GetResponse();

Stream sr = myResponse.GetResponseStream();

// retrieve session id

char[] sep = { ‘;’ };

String[] headers = myResponse.Headers[“Set-Cookie”].Split(sep);

for (int i=0; i <= headers.Length-1; i++)

{

if (headers[i].StartsWith(“JSESSIONID”))

{

sep[0] = ‘=’;

SessionID = headers[i].Split(sep)[1];

break;

}

sr.Close();

myResponse.Close();

}

catch (WebException webException)

{

}

catch (Exception ex)

{

}

// send back the session id that should be passed to subsequent calls

// to webservices

return SessionID;

}

That’s it..

The remote server returned an error: (500) Internal Server Error while using Siebel CRM On Demand Web Services.

I got this error while trying to Logging In to the Web Services Session using .NET. Spent whole day for finding out what could be the reason behind the issue. Finally came to know the issue was because of the username being not passed correctly.

The username that we were passing was in this particular format that we would normally do

‘orgname-devusername’

Whereas it was expecting it in this format

‘orgname-dev/username’

i.e. forward slash instead of the back slash.

I hope it helps!

Customizing Custom Web Part Menu in SharePoint

Any standard web part within SharePoint would have menu options like Minimize, Close, and Modify Shared Web Part. We can even add our own custom menu options over there. They are referred to as verbs in web part’s context. We could add three types of web part menu verbs.

Client Side –We could specify JavaScript over here.

Server Side – We can attach event handler over here.

Both – We could have both JavaScript and event handler specified.

Let’s take a simple example where we would be adding all the above three kind of verbs.

Create a web part project within Visual Studio.

Put the following code for web part,

It would have a text box that would show the text set using the event handler specified in the server side verb.

[Guid(“172bc4c1-1c5d-49cd-93bc-1874acbbb9c8”)]

public class WebPartMenuVerbWebPart : System.Web.UI.WebControls.WebParts.WebPart

{

public WebPartMenuVerbWebPart()

{

}

protected TextBox txtInfo;

protected override void CreateChildControls()

{

txtInfo = new TextBox();

this.Controls.Add(txtInfo);

}

public override WebPartVerbCollection Verbs

{

get

{

// Client side verb

WebPartVerb clientSideVerb = new WebPartVerb(“clientID”, “javascript:alert(‘Hello World from Java Script Verb!’);”);

clientSideVerb.Text = “Client Side Verb”;

// Server side verb

WebPartVerb serverSideVerb = new WebPartVerb(“serverID”, new WebPartEventHandler(ServerVerbEventHandler));

serverSideVerb.Text = “Server Side Verb”;

// Verb for both client side and server side

WebPartVerb bothSideVerb = new WebPartVerb(“bothID”, new WebPartEventHandler(ServerVerbEventHandler), “javascript:alert(‘Hello World from Java Script Verb!’);”);

bothSideVerb.Text = “Both Side Verb”;

WebPartVerbCollection wbVerbCollection = new WebPartVerbCollection(base.Verbs, new WebPartVerb[] { clientSideVerb, serverSideVerb, bothSideVerb });

return wbVerbCollection;

}

protected void ServerVerbEventHandler(object sender, WebPartEventArgs args)

{

txtInfo.Text=“Hello world from Server Side Verb”;

}

That’s it …