That is unfortunate.  It is the main reason we are probably going to have to say goodbye to Infragistics. 

Our users construct queries and the results get poured into the grid where they may need to group, filter, multi-col sort,  etc.  We allow the user to turn these feature off and on from a popup menu.

So, we do not know in advance what our users may want to do.   Therefore, according to you we would have to use WebHierarchicalDataGrid as our grid surface, in case they want to group.  We have found that binding a single table to that grid to be a kludge at best and that the grid itself to be short of the feature set we used to engage in the old UltraWebGrid.

So long old friend. 

Taz,

We're in the same boat as the other user.  We have been incredibly disappointed and frustrated by Infragistics new WebDataGrid and the lack of features compared to the UltraWebGrid.  The scenario is simple.  We want a grid that I can bind to a non-hierarchical data source that supports grouping.  You know, like the UltraWebGrid did.  Why on earth do you tie grouping and a hierarchical data source together?  It wasn't required in the UltraWebGrid.  My data isn’t hierarchical and doesn’t need to be.  I need to be able to allow users to simply group data from a flat table.  Why do you need “to understand more about your scenarios”? 

This is just one of many features that the UltraWebGrid offered that the "new", far inferior, WebDataGrid fails to deliver.  Infragistic’s decision to refuse to continue to adequately support the UltraWebGrid despite the fact that the “replacement” is woefully inferior and lacking in comparable features is going to drive many customers away.   The overall lack of quality in the new controls in general is really quite disappointing.  Given our experience across the board with the “new” controls combined with the low level of support, we are unlikely to ever buy a control from Infragistics again.

H sbeeler,

When you are grouping the data, it becomes hierarchical rendering.  You do not have to make your data hierarchical.  You can keep it flat and simply bind it to the WebHierarchicalDataGrid through a WebHierarchicalDataSource.  This will handle the job of giving the grid the data in the right format.  In 11.1, Column Moving, Column Resizing, and Row Edit Template will officially be supported in the WebHierarchicalDataGrid.  We are also adding checkbox and unbound fields to bring the grids features that had thus far been missing.  If there is a feature that you need to have, let us know so that we can prioritize them correctly to please you, the customer.  In the meantime, there may be a workaround that we can give to you.  As Taz said, reach out to him with features that you require in the WebDataGrid or WebHierarchicalDataGrid.

regards,
David Young 

When will 11.1 be released with the missing features?

Hi,

11.1 will be released in early June.  

-Dave

Wow.  We were originally told early April.  Then early May.  Then mid-May.  Now early June. 

Good job managing expecations and meeting deadlines.  As far as we're concerned, 2011.1 is vaporware.  It will now be delivered too late for us to meet our own deadlines for our customers.  So thanks IG for stringing us along.

And don't tell us to use a control that doesn't have all the features needed that existed in your previous product.  Neither the WebDataGrid nor the heirarchical grid currently provide the needed functionality in their current, shipping forms.  Promises for features in as yet undelivered versions are just promises...  and we can't build applications using your promises.  Given that the WebDataGrid and Heirarchical grid aren't ready for prime-time, support for the UltraWebGrid should never have been discontinued.  And why the UltraWebGrid (which could do it all) was split into two separate grids that don't have the same features is beyond anyone's comprehension. 

Just a couple more nails in the coffin for those of us fed up with Infragistics lack of focus.

One clarification to my question, we databind directly to our DataSet object and set the grid's DataMember to the name of the table we are targetting in that DataSet.  Is binding directly to the DataSet not supported?

Hi Dave,

I have found that I can only get the WebHierarchicalDataGrid to do this binding when I intially load the page.  In my use-case, the user may select new queries during the life of the page and I need to reissue the "GetData" and bind the new results.  What I find is that, subsequent databinds appear to work in the code-behind, but the results do not change on the browser surface when control is returned to the client.

Any ideas? 

Hi Scott, 

Sorry about the delay in release dates. Drop me an email, and I can send you a pre-release 11.1 build. 

murtazaa@infragistics.com

-Taz.