[Solved] Groups doesn't close correctly when a detail view is defined

[Sébastien]

I created a grid with groupeable columns and detailview for each row as follow :

@model List<DemoGridGrouping.Models.Data>
@{
    ViewBag.Title = "Home Page";
}

@(Html.Telerik().Grid(Model).Name("LogGrid")
.Columns(columns =>
{
    columns.Bound(o => o.UserName).Title("User").Width(100).Aggregate(agregate => agregate.Count()).GroupHeaderTemplate(@<text>@item.Title: @item.Key (@item.Count)</text>);
    columns.Bound(o => o.Title).Title("Title").Aggregate(agregate => agregate.Count()).GroupHeaderTemplate(@<text>@item.Title: @item.Key (@item.Count)</text>);
})
.Scrollable(c => c.Height(450))
.Filterable()
.Groupable()
.Resizable(resize => resize.Columns(true))
.Reorderable(reorder => reorder.Columns(true))
.DetailView(details => details.Template(data=>{   }))
)

At runtime, I create a group (dragging a column at the to of the grid) and, then I want to close on of the created group. 
It only the first row disappear and the other row of the same group are still visible.
If you comment the .DetailView(...) line, the groups works fine.

I wanted to know if there is a bug or if I did something wrong using group or/and Details View.

I attach a sample project to reproduce the problem.

I use Telerik ASP.NET MVC 2011.2.712 (but I also reproduce the bug on 2011.1.315). The problem is on all my browser (ie 9/ff 5/chrome 12) running on Win7.

Thanks in advance for your answer.

[Rosen]

Hi Sébastien,

I was able to observe the behavior you have described. However, we have managed to address it and the build which contains the fix can be downloaded from the latest internal builds page in your account. I have also updated your telerik points.

Kind regards,
Rosen
the Telerik team

[Andy]

Hello,  Am i right in thinking then that this fix does not appear in the latest open source build? (version 2011.2 712)

If the issue has not been resolved in the latest open source build.  Is there a work around that can be implemented?

Sorry just re-read the details in the original post.  The problem does exist in the latest open source version

[Sébastien]

I use the 2012.2.715 version and it works correctly on my application now.