Thank you, Mike!

Hello,

The initial call to the server for the root level data is happening twice because you have you call databind after you setup the igTreeGrid. Like so:

ds.dataBind();

The igTreeGird will call databind itself, you do not need to call it an additional time. Currently there isn’t a way to access the dataLevel from the customEncodeUrlFunc, so the way to do this be to us the rowexpanded/rowexpanding.

Mike,

Thank you! I came up with a pretty much the same solution:

            var ds = new $.ig.TreeHierarchicalDataSource({
                dataSource: '/Home/GetTreeDataPlain',
                treeDS: {
                    customEncodeUrlFunc: function (rec, expand) {
                        return '/Home/GetTreeDataPlain?id=' + rec.ID.toString() + '&name=' + rec.LastName;
                    }
                }
            });

            $treegrid.igTreeGrid({
                dataSource: ds,
                childDataKey: 'Employees',
                ...
            });

            ds.dataBind();

There is one issue with that, though: the initial call to the server for the root level nodes is issued twice for some reason. (A bug?)

One more question about customEncodeUrlFunc: is there a way to pull the current data level from the rec argument object? It seems that it's present inside that object (__ig_options.dataLevel), but I am not sure how to get that value. As a workaround I subscribed to rowExpanding event where I can pull it from ui.dataLevel and store in an external variable, but it seems like a hackey way of doing things.

Hello,

I have done some further looking into this matter and it seems like the datasource is having an issue. As an alternate way to achieve the behavior you can do the following code after you initialize the treeGrid:

$treegrid.data("igTreeGrid").dataSource.settings.treeDS.customEncodeUrlFunc = function (record, expand) {
                return "/Home/GetTreeDataPlain?stuff='howdy'"
            }

Hello,

Thank you for your patience. I am currently looking into this behavior with my team to see why this happening and how to achieve the intended behavior. I will continue to look into this matter and update you with my progress.