I don't know what script error you are seeing in fiddle page. Anyways see the attached document which has no script error but issue still exist. Please let me know what wrong here. your example is not working on my machine as it using localhost and I don't want to make sure of ig.Loader.

-Manish

Still same issue after fixing that.

http://jsfiddle.net/eSMWt/

-Manish

Hello Manish Dalal,

As per my investigation, I noticed that when using the igLoader to load the resources needed, the sample works as expected; otherwise, the behavior you described occurs. I am currently, investigating this anomaly and will update the thread once I receive more information.

The behavior is correct.  If you want to have different column layout for the same data source then you cannot use AutoGenerateColumns.  Since the Data Source provider looks at the entire schema, it noticed that you had two additional columns in one object, but not the other.  If you manually create the columns yourself then it will work.  Otherwise specify the same template for the first grid like you did for the second.

They are two different data source. First one is using data.grid1 and second is using data.grid2. They are two different data source. If auto layout is generated fine for parent row than why it is not generating for child row.

If you change the order of  grid than it works , 

$("#DetailPaneDetailsUserDefined").igGrid({
dataSource: data.grid2
});
$("#DetailPaneDetailsLicensePlates").igHierarchicalGrid({
dataSource: data.grid1,
autoGenerateLayouts: true
});

We have metadata driven UI, I cannot change the order. I think this a bug.

-Manish

So you are absolutely correct.  I misread several parts of the code.  I saw autoGenerateColumns instead of autoGenerateLayouts.  This is indeed a bug.

Hi Manish Dalal,

I have investigated the issue regarding Columns of second igHGrid appear as child of first igHGrid. I have asked our Product Development to examine this further.  To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 172064.  The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution. 

I will be sure to update this forum thread once I receive more information about the results of their investigation.

Ok it works with 1.8.18 version but i still think this i an issue with ignite ui.  As Ignite UI support jquery UI 1.10.3

http://code.jquery.com/ui/1.10.3/jquery-ui.min.js

Its igrniteUI responsibility to write API which works with supported version.

-Manish

Thanks!

So I'm reopening my case again.  (CAS-137183-M8W1R2)

-Manish