updating GridView cell background color

[=?Utf-8?B?bWljaGFlbCBzb3JlbnM=?=]

I understand how to connect a SqlDataSource to a GridView and have a nice
data-connected, paginated web page generated with virtually no coding.
Starting from that base, I would like to add an extra column to the GridView
and do two things: for each row, based on the value of another column, insert
a string in the new column cell and set the background color of the new
column cell. Suggested approaches would be appreciated.

[=?Utf-8?B?TGFkaXNsYXYgTXJua2E=?=]

Hi Michael,
you can create handler for RowDataBound event of your GridView. In this
handler you will be able to access and modify cells and data of your current
row.

protected void myGridView_OnRo wDataBound(obje ct sender, GridViewRowEven tArgs
e)
{
if (e.Row.RowType = DataGridRowType .DataRow)
{
// e.Row.Cells contains collection of server side td elements, you can
fill
// text property or work with collection of controls inside this element
e.Row.Cells[INDEX_OF_YOUR_C OLUMN].Text = EvalMyField(e.R ow.DataItem );
// DataItem contains source of data for this row, it is object used by data
source to fill your row
// you can also modify css style for your elelment
e.Row.Cells[INDEX_OF_YOUR_C OLUMN].Attributes.Add ("style", ".......");
}
}

Regards,
Ladislav

"michael sorens" wrote:

I understand how to connect a SqlDataSource to a GridView and have a nice
data-connected, paginated web page generated with virtually no coding.
Starting from that base, I would like to add an extra column to the GridView
and do two things: for each row, based on the value of another column, insert
a string in the new column cell and set the background color of the new
column cell. Suggested approaches would be appreciated.

[=?Utf-8?B?bWljaGFlbCBzb3JlbnM=?=]

Splendid! I had to test for DataControlRowT ype.DataRow rather than
DataGridRowType .DataRow, but that essentially did most of what I needed.

Now how do I position the new column as the right-most column?
I first tried adding a new column of type Template in the visual designer.
This new column became the first column. I tried the same thing
programmaticall y by calling gridView.Column s.Add() in the PageLoad handler
and it also became the first column. I then switched to Columns.Insert( ) but
in the PageLoad handler the binding has not yet occurred, hence column count
is still 0. When the binding occurs, the columns are added to the right,
again leaving my new column as the left-most. What event handler would give
me access to the GridView after the columns have been loaded so I can then
add my new column where I want?

[Walter Wang [MSFT]]

Hi Michael,

I'm glad that you've solved your first issue.

For the second question, have you tried to add the column in GridView's
DataBound event? In this event, the data has been bound and those columns
are generated, therefore you can add your column to the right-most.

Please let me know the result. Thanks.
Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?bWljaGFlbCBzb3JlbnM=?=]

I had tried the DataBound event because that seemed to be the right place.
But the results were the same. To see why, here is the output of a test
program that includes a GridView with 5 columns from design-time where I
attempt to add 3 more columns at run-time.

Curiousities:
(1) The column count shows 0, not 5, upon entering the DataBound event
handler.
(2) After adding the 3 new columns, the column count is then 3, not 8, at
the conclusion of the event handler.
(3) The DataBound event is triggered twice so I had to add the
gridInitialized switch to prevent adding the columns again.
(4) The column count still shows 3 on the second pass through the DataBound
event handler, yet the grid displays with all 8 columns (the 3 new ones are
left-most).
With novice-like bravado I will say that it sure looks like the event is not
firing when it is supposed to!

=============== =============== =============== ====
ENTERING GridView_DataBo und: Column count=0, gridInitialized =False,
IsPostBack=Fals e
ENTERING AddCol[1]
LEAVING AddCol
ENTERING AddCol[2]
LEAVING AddCol
ENTERING AddCol[3]
LEAVING AddCol
LEAVING GridView_DataBo und: Column count=3, gridInitialized =True,
IsPostBack=Fals e
ENTERING GridView_DataBo und: Column count=3, gridInitialized =True,
IsPostBack=Fals e
LEAVING GridView_DataBo und: Column count=3, gridInitialized =True,
IsPostBack=Fals e
=============== =============== =============== ====

Here is the sample program:
=============== =============== =============== ====
public partial class _Default : System.Web.UI.P age
{
private int numDays = 3;
private DateTime firstDisplayDat e = new DateTime(2007, 1, 3);
private List<TemplateFi eldchartCol = new List<TemplateFi eld>();
private bool gridInitialized = false;

protected void GridView1_DataB ound(object sender, EventArgs e)
{
Out("ENTERING GridView_DataBo und: Column count=" + GridView1.Colum ns.Count
+ ", gridInitialized =" + gridInitialized + ", IsPostBack="+Is PostBack);
if (!gridInitializ ed && !IsPostBack)
{
for (int i = 0; i < numDays; i++) { AddCol(); }
gridInitialized = true;
}
setDates();
Out("LEAVING GridView_DataBo und: Column count=" + GridView1.Colum ns.Count
+ ", gridInitialized =" + gridInitialized + ", IsPostBack=" + IsPostBack);
}

private void setDates()
{
DateTime d = firstDisplayDat e;
foreach (TemplateField t in chartCol)
{
t.HeaderText = d.ToString("ddd MM/dd");
d = d.AddDays(1);
}
}

private void AddCol()
{
TemplateField tField = new TemplateField() ;
chartCol.Add(tF ield);
Out("ENTERING AddCol["+chartCol.Coun t+"]");
GridView1.Colum ns.Add(tField);
Out("LEAVING AddCol");
}

private void Out(string s)
{
Response.Write( s + "<br>\n");
}

}
=============== =============== =============== ====

[=?Utf-8?B?bWljaGFlbCBzb3JlbnM=?=]

(1) If I set AutoGenerateCol umns = false, I presume that means I have to
manually add *all* columns? If so, do you have a code sample showing how I
would add columns bound to the original select statement (which were created
automatically before)?
(2) In your sample CreateColumns, am I correct that you are showing one
bound field and one new field? So does this also need to manually create all
columns that were bound from the select statement? Is "au_lname" one of the
items in the select list? Not really sure how this relates to the original
behavior where the framework did everything for me...

[=?Utf-8?B?bWljaGFlbCBzb3JlbnM=?=]

(1) If I set AutoGenerateCol umns = false, I presume that means I have to
manually add *all* columns? If so, do you have a code sample showing how I
would add columns bound to the original select statement (which were created
automatically before)?
(2) In your sample CreateColumns, am I correct that you are showing one
bound field and one new field? So does this also need to manually create all
columns that were bound from the select statement? Is "au_lname" one of the
items in the select list? Not really sure how this relates to the original
behavior where the framework did everything for me...

[Walter Wang [MSFT]]

Hi Michael,

(1) That's right, if AutoGenerateCol umns=False, you will need to manually
add all columns. You can do it declaratively in ASPX:

<asp:GridView ID="GridView1" runat="server"
AutoGenerateCol umns="False" DataKeyNames="a u_id"
DataSourceID="S qlDataSource1" OnDataBound="Gr idView1_DataBou nd"
OnDataBinding=" GridView1_DataB inding">
<Columns>
<asp:BoundFie ld DataField="au_i d" HeaderText="au_ id"
ReadOnly="True" SortExpression= "au_id" />
<asp:BoundFie ld DataField="au_l name" HeaderText="au_ lname"
SortExpression= "au_lname" />
</Columns>
</asp:GridView>
or you can add at runtime, in either case, you need to know the DataField
name ("au_id" and "au_lname" in above example).

It's possible to duplicate the functionality of how GridView's
AutoGenerateCol umns does, however, it's much complicated and I don't think
it's worth the effort doing this: the GridView needs to support various
data source such as DataSource controls (ObjectDataSour ce, SqlDataSource,
etc.) and IEnumerable data, you can take a look at GridView's code using
Reflector (http://www.aisto.com/roeder/dotnet/) if you're interested.

(2) Yes one field is a data bound field, just like above declarative
example shows.

As I explained above, I think if you need to set the
AutoGenerateCol umns=True, then I suggest you create a customized GridView
to add your custom columns; if you set AutoGenrateColu mns=False, then you
need to manually setup those columns in ASPX or code, but you need to know
the data field names.
Hope this helps.
Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?bWljaGFlbCBzb3JlbnM=?=]

This all seems rather more convoluted that it should need to be. After all,
the GridView.Column s collection has both an Add and an Insert method. I am
rather skeptical that you are, in essence, saying that either or both of
those and the DataBound event do not work as advertised.

[Walter Wang [MSFT]]

Hi Michael,

I fully understand your concerns here. Please let me try to explain more
about the limitation here.

First, I apologize if my initial reply indicated that this could be done in
the DataBound event, which I later found out is not correct.

You are right that the columns has Insert and Add method, however, it's all
about the correct timing to call these methods if you need to position your
manually added column with the auto generated columns. Currently GridView
doesn't expose an appropriate event that could let you do this after the
columns are auto-generated, in other words, from the WebForm that hosts the
GridView, we don't have a correct event or time to call
GridView.Column s.Add or Insert.

On the other hand, the GridView internally does calls a virtual method
named 'CreateColumns' which can be overriden to append new columns after
the auto-generated columns.

I agree that this is a limitation of the GridView. I will make sure this
feature request is correctly forwarded to product team for future version's
improvement. In the meanwhile, you're also welcome to submit your feedback
at http://connect.microsoft.com/Main/co...ContentID=2220
which is monitored by product team directly and other community members can
also vote on the reqeust.

Thanks again for your great feedback!
Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.