Ok, I changed the DisplayLayout ViewType to Hierarchical, but the behaviour stayed the same: The webgrid did not even populate the parent band (no columns shown in the designer) and the DataMember combo does not show any (it should diplay the names of each of the two views of the WHDS I suppose).

What could be wrong?

Thanks a lot.

Thanks for your kind reply. 

Well, the whole idea of using the WHDS was to have design-time support; that is, I would have expected to be able at design-time to edit the properties of the columns of both bands -as if it were a wingrid bound to a hierarchical typed dataset. I believe that that's one of the features of WHDS, if I am not mistaken.

What's more, I would have bound the webgrid at runtime directly to a non-typed dataset had I known that design-time support is not given in the described scenario. Unless of course that something is missing in my code.

Is it impossible to have design-time support for a webgrid bound to a WHDS as described?

It has been almost 15 days. Can someone please answer my previous question?

Thanks a lot.

I too am experiencing this behavior. Neither band populates in Design time with exactly the same data setup as above. If I switch the DataSourceID to either of the ObjectDataSources, the band populates correctly, but when I switch it back to the WHDS, no band data is available in the designer.

Now that version 8.3 is out, does the problem persist?

I have the same issue with 9.1. Would like to see this answered as well.

I have the same issue with 8.3. This is really an important and clear question -

Is there a way to get design-time support for hierarchical data in WebGrid, using CLF 2.0?