Hello Son,

I was not able to reproduce your initial problem using your code you pasted into a sample.
Could you try and see if you are experiencing the same problem on my sample that I have attached.

If you are not seeing the issue you have I would suggest sending a working sample. It could be as simple as possible, so that it highlights the same issue you have. Otherwise it is hard to replicate the same conditions as the ones you have.

Regards,
Svetoslav Krastev,
Infragistics

I get this error when I attempt to expand the hierarchical grid from a second dataset. The first dataset works fine. Any subsequence dataset get this error when parent is click to expand and view the child.

div.data("igScroll")._content=this.element;div.igScroll("refresh");div.igScroll("option","scrollOnlyVBar",false);div.

Unable to set property '_content' of undefined or null reference

Here the code. I also noticed the expand and collapse icon disappear after the initial binding. On the second binding (another query), the icon would disappear.

function BindGrid(ds) {

try {

$("#gridClassLimit").igHierarchicalGrid({
width: "100%",
dataSource: ds,
dataSourceType: "json",
responseDataKey: "d",
autoGenerateColumns: false,
//primaryKey: "UniqueID",
//initialDataBindDepth: 1,
height: "425px",
//rowExpanding: function (e, args) {
// alert('expanding');
//},
features: [
{
name: "Sorting",
inherit: true
},
{
name: "Paging",
pageSize: 5,
//type: "local",
//inherit: true
pageSizeDropDownLocation: "inpager"
},
//{
// name: "Filtering"
//}
],

columns: [
{ key: "UniqueID", headerText: "UniqueID", hidden: true},
{ key: "CompanyName", headerText: "Company Name", width: "20%" },
{ key: "SystemName", headerText: "System Name", width: "20%" },
{ key: "SubSystemName", headerText: "Subsystem Name", width: "20%" },
{ key: "LineNo", headerText: "Line No", width: "20%" },
{ key: "LineDescr", headerText: "Line Description", width: "20%" }
],

//autoGenerateLayouts: false,
columnLayouts: [{
key: "ClassLimitChild",
responseDataKey: "",
autoGenerateColumns: false,
autofitLastColumn: false,
primaryKey: "UniqueID",
width: "100%",
height: "300px",
columns: [
{ key: "UniqueID", headerText: "UniqueID", width: "0%", hidden: true },
{ key: "RouteDescription", headerText: "Route Description", dataType: "string", width: "250px" },
{ key: "SeriesDescr", headerText: "Series Description ", dataType: "string", width: "250px" },
{ key: "BeginSeries", headerText: "Begin Series", dataType: "number", width: "150px" },
{ key: "BeginStation", headerText: "Begin Station", dataType: "number", width: "150px" },
{ key: "EndSeries", headerText: "End Series", dataType: "number", width: "150px" },
{ key: "EndStation", headerText: "End Station", dataType: "number", width: "150px" },
{ key: "BeginLat", headerText: "Begin Lat.", dataType: "number", width: "150px" },
{ key: "BeginLon", headerText: "Begin Long.", dataType: "number", width: "150px" },
{ key: "EndLat", headerText: "End Lat.", dataType: "number", width: "150px" },
{ key: "EndLon", headerText: "End Long.", dataType: "number", width: "150px" },
{ key: "LengthMiles", headerText: "Length Miles.", dataType: "number", width: "150px" },
{ key: "ClassRating", headerText: "Class Rating", dataType: "string", width: "150px" },
{ key: "DivisionCode", headerText: "Division", dataType: "string", width: "150px" },
{ key: "OperatingArea", headerText: "Area", dataType: "string", width: "250px" },
{ key: "DistrictCode", headerText: "District", dataType: "string", width: "250px" }
],
features: [
{
name: "Paging",
pageSize: 10,
//type: "local",
//inherit: true
pageSizeDropDownLocation: "inpager"
},

]
}]

});

//ShowHideBusyIndicator(false);

}
catch (ex) {
alert(ex.message);
//ShowHideBusyIndicator(false);
}

}

Hello Son,

Removing the PrimaryKey of the main grid is not considered advisable in conjunction with the Updating feature for example, because then it cannot function as expected.

Also PrimaryKey shouldn't affect the child grid scrollbars or any scrollbars in particular. If you still would like to either send your full grid configuration or quick sample where this can be seen, so we could investigate why was this caused.

Regards,
Svetoslav Krastev,
Infragistics

I got it working after removing the primarykey tag from the parent table.