Skip to main content

Super Useful Tips on Using DevExpress ASPxGridView

I've been using DevExpress's ASPxGridView on a fairly big ASP.Net project for the past few months. When I started using it, I was really frustrated. The documentation was written more like a class reference guide and the tutorials were fairly basic in nature.

The real MEAT of the controls didn't seem to be there - all this great potential but where?

The Community forums was a great place to look for details but as with many communities, it's hard to find all the answers. 

Hopefully, this post will help identify some of the areas where developers may be having some problems:

Fixing Edit Forms
1. Edit Form Column Layouts
The ASPxGridView lets you do direct "form" editing but when you first do it, the boxes usually go two per line. To resolve this, add
                              <SettingsEditing EditFormColumnCount="1" />
right under the grid definition.

2. Changing Edit Captions
You have a column that is titled Years but in the edit form, you want it to say "Years working for company". Within the column definition, add
<dxwgv:GridViewDataTextColumn FieldName="Years" Caption="Years"/>
          <EditFormSettings Caption="Years working for the company " />
</dxwgv:GridViewDataTextColumn>


Grouping Grids
The ASPxGridView lets you group the grids automatically.

1) Call grid.ExpandAll( ) right after the DataBind (or the Page_Load) to automatically open the groups (by default, they are closed)

2) The Group header starts by showing the name of the Group a colon and then the name. In the Grid definition, add"
Settings-GroupFormat="{1} {2}"

Commands
One thing I didn't like about the Grid View was that it would add New/Edit/Delete buttons on each row. Why show New on each one? I originally put a hyperlink on the top of the grid but instead, I've started to use the HeaderTemplate option instead.

Here's my initial Column set:
                    <Columns>
                        <dxwgv:GridViewCommandColumn VisibleIndex="0">
                            <NewButton Text="New" Visible="false">
                            </NewButton>
                            <EditButton Text="Edit" Visible="true">
                            </EditButton>
                            <DeleteButton Text="Delete" Visible="true">
                            </DeleteButton>
                            <HeaderTemplate><dxe:ASPxHyperLink ID="lblNew" runat=server Text="New" Font-Underline=true Cursor=pointer><ClientSideEvents Click="function(s,e){officers.AddNewRow();}" /></dxe:ASPxHyperLink></HeaderTemplate>
                        </dxwgv:GridViewCommandColumn>

The end result looks like this


Grid Form Validation
You can easily make a field mandatory in a grid by setting the IsRequired property to true. But there are two gotchas with this. By default, this puts a little exclamation mark by the field when you hit the Update button. The ErrorText property is then put into the tooltip.

Set the ErrorDisplayMode property to Text instead of the default which is ImagewithTooltip.

Another way to better manage this process is to put the validation settings directly into the code instead of the property settings.

loCol = grid.Columns(0)

            With locol.PropertiesTextEdit.ValidationSettings
                .RegularExpression.ValidationExpression = regexp
                .ErrorDisplayMode = DevExpress.Web.ASPxEditors.ErrorDisplayMode.Text
                .RegularExpression.ErrorText = msg
                .RequiredField.IsRequired = True

            End With

The above code also shows one of the other cool tips - instead of trying to validate the text after, by setting the ValidationExpression property, the input can be immediately validated via Regular Expression.

Column Widths
By default, the ASPxGridView will resize the widths based on the content. Some of our users found this disorienting when they edited the grid - because it would constantly change. Solution? Explicitly set the widths of each column.

I'm sure there are a lot more and some of the above are likely pretty obvious but I wish I had known about them when I first got started. I'll be adding to this post (or creating new ones) as I move forward.

The other cool part about devExpress is that a number of their developers are on Twitter, making it easier to find them and get help.


Comments

Anonymous said…
found your tips searching for some solutions! Nice!

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP