Thanks a lot.

Hi Jérôme,

You are correct about this.  I have submitted bug 111888 for this.  The problem it seems is that we might skip generating the layouts on the server, but it still tried on the client.  This should be in the first service release.  If you want to fix this in the meantime, you could modify the list view javascript inside

dataBind: function() { for the igListView (not igList).

Change
if (this.options.autoGenerateLayouts) {
to
if (this.options.autoGenerateLayouts === true) { 

regards,
David Young 

Hi, I've a AutoGenerateLayouts (not AutoGenerateChildLayouts) on the top level and that does not work for me...

<%= Html.InfragisticsMobile().ListView<Ecurie>()
                .DataSource(Model)
                .ID("myListView")
                .AutoGenerateLayouts(false)
                //.Inset(true)
                .ImageMode(Infragistics.Web.Mvc.Mobile.ImageMode.ThumbNail)
                //.ShowCount(false)
                //.ItemTheme("b")
                .Bindings(b =>
                {
                    b.HeaderKeyFor(e => e.Nom)
                        .ImageUrlKeyFor(e => e.UrlImage)
                        .DescriptionKeyFor(e => e.Description)
                        .CountKeyFor(e => e.NbTitres)
                        .TextKeyFor(e => e.Resume)
                        .CustomBindingFor(e => e.Nationalite); //Utile pour des action en local sur les filtres/classements.
                        //.NavigateUrlKeyFor(e => e.Url);//mettre en // si multi-level

                ...

Thanks in advance,

Jérôme.

Hi CubeRaptor,

If I understand your question correctly, you do not want us to generate the child layout?  You should set AutoGenerateChildLayouts to false on the top level.  Whenever, there are children present, the navigate url is ignored as we need to navigate to a dynamic sub page holding the children instead.

regards,
David Young