Null Values in ItemUpdating Event

[clickon]

I have a DetailsView control and when it get's updated i send an email
containing the new details. I have used the ItemUpdating event handler for
the DetailsView and i am populating the MailMessage.Bod y property with a
string variable which i build up using something like

String strMessageBody = "Field1 = " + e.NewValues["Field1"].ToString() +
"\nField2 = " + e.NewValues["Field1"].ToString();

This works fine apart from when one of the fields i am refering to is blank.
What i expected to happen is the e.NewValues["Field1"].ToString would give
me a blank string. However it seems that if the value coming from the
DetailsView is null for Field1 then e.NewValues["Field1"] doesn't exist.

Is there an easy way round this, i am putting the values of about 10 fields
into one string variable, i want to avoid 10

if (e.NewValues["Field1"] != null)
{
strMessageBody = strMessageBody + "Field1 = " +
e.NewValues["Field1"].toString();
}

[Flinky Wisty Pomm]

If you just want to avoid duplicated code, why not move it into another
method?

public string getField(IOrder edDictionary values, string key)
{
return values.Contains Key(key) ?
string.Format(" {0} = {1}", key, values[key]) :
string.Empty;
}

then it's a simple case of string strMessageBody = getField("field 1") +
getField("field 2")...

[clickon]

It's not so much code duplication i am tring to avoid as having to do a load
of comparisons to see if a particular value is set or not. The problem with
passing e.NewValues("So meField") to a function/method is that if SomeField is
set to null in the DetailsViews control then rather than there being
e.NewValues("So meField") with a value of null, it simply does not exist. You
get a "Object reference not set to an instance of an object" if you try to do
something such as e.NewValues("So meField").ToStr ing().
"Flinky Wisty Pomm" wrote:

If you just want to avoid duplicated code, why not move it into another
method?

public string getField(IOrder edDictionary values, string key)
{
return values.Contains Key(key) ?
string.Format(" {0} = {1}", key, values[key]) :
string.Empty;
}

then it's a simple case of string strMessageBody = getField("field 1") +
getField("field 2")...

[clickon]

I have solved the problem, you simply set ConvertEmptyStr ingToNull="Fals e",
in all of the TemplateFields of the DetailsView.

"clickon" wrote:

It's not so much code duplication i am tring to avoid as having to do a load
of comparisons to see if a particular value is set or not. The problem with
passing e.NewValues("So meField") to a function/method is that if SomeField is
set to null in the DetailsViews control then rather than there being
e.NewValues("So meField") with a value of null, it simply does not exist. You
get a "Object reference not set to an instance of an object" if you try to do
something such as e.NewValues("So meField").ToStr ing().
"Flinky Wisty Pomm" wrote:

If you just want to avoid duplicated code, why not move it into another
method?

public string getField(IOrder edDictionary values, string key)
{
return values.Contains Key(key) ?
string.Format(" {0} = {1}", key, values[key]) :
string.Empty;
}

then it's a simple case of string strMessageBody = getField("field 1") +
getField("field 2")...