Table of Contents
- Introduction
- Business Requirement
- Solution
- Database Implementation
- Recursive Function
- Conclusion
- Reference
ASP.NET Treeview control is the most used server control for representing tree view hierarchy data structure. Most of the time, we get requirements related to hierarchical tree structure of data representation; this becomes more complicated and complex if we've depth of leaf node to extreme extent. In such scenarios, we may have to look at generic solution. This article will help a developer to use the below logic or implementation to tackle similar situations.
Say for example, we've business problem statement of representing certain family or category in hierarchical fashion. In such case, iteration through XML tree or structured database becomes a challenge. Even parsing is one part of the problem and then representing it in graphical view of that hierarchy pattern.
Note: Here, the challenge is data structure are not hardcoded and any point of time new leaf node or parent node may be added at runtime. Hence having XML structure will be bit challenge as parsing, locating parent node and updating XML data will put additional overhead on programmer.
Approach to be followed:
- Structure data in desired hierarchical format-Datatable schema.
- Establish parsing logic. Write recursive Function
- Bind it to Tree view control.
Important contributing factors are here to create well data table structure and binding it to tree view control.
- ASP.NET TreeView Control
- Technology
- ASP.NET
- SQL Server 2005
Create table tbl_Tree_Hierarchy:
Create Stored procedure ssp_get_hierarchy: This will give Node_ID its child information and level or depth of leaf node or branch it belongs to.The below is the result set of the above stored procedure. The best use of Common table expression in SQL Server 2005 to refer recursive dataset using WITH Clause:
Create recursive function to traverse through hierarchical tree data structure. This functionality is developed using ASP.NET 2.0 and the recursive function can be avoided using CSharp .NET 3.5 using LINQ. Using anonymous delegate, we can compare the collection objects with some logical condition. Once the result set is filtered, it can be traversed and can be added as object item to tree view control.
Create HierarchyTrees generic collection which contains Htree objects.
public class HierarchyTrees : List <HierarchyTrees.HTree>
{
public class HTree
{
private string m_NodeDescription;
private int m_UnderParent;
private int m_LevelDepth;
private int m_NodeID;
public int NodeID
{ get {return m_NodeID;}
set { m_NodeID=value; }
}
public string NodeDescription
{
get { return m_NodeDescription; }
set { m_NodeDescription = value; }
}
public int UnderParent
{
get { return m_UnderParent; }
set { m_UnderParent = value; }
}
public int LevelDepth
{
get { return m_LevelDepth; }
set { m_LevelDepth = value; }
}
}
}
PopulateTreeview() function will fetch recordset from database and will populate the generic collection tree.
private void PopulateTreeview() {
this.tvHierarchyView.Nodes.Clear();
HierarchyTrees hierarchyTrees = new HierarchyTrees();
HierarchyTrees.HTree objHTree=null;
using (SqlConnection connection = new SqlConnection
(@"Persist Security Info=False;Integrated Security=SSPI;
database=FamilyTree;server=[Local]"))
{
connection.Open();
using (SqlCommand command =
new SqlCommand("SSP_GET_HIERARCHY", connection))
{ command.CommandType = System.Data.CommandType.StoredProcedure;
SqlDataReader reader = command.ExecuteReader
(System.Data.CommandBehavior.CloseConnection);
while (reader.Read())
{
objHTree=new HierarchyTrees.HTree();
objHTree.LevelDepth = int.Parse(reader["LEVEL_DEPTH"].ToString());
objHTree.NodeID = int.Parse(reader["NODE_ID"].ToString());
objHTree.UnderParent = int.Parse(reader["UNDER_PARENT"].ToString());
objHTree.NodeDescription = reader["NODE_DESCRIPTION"].ToString();
hierarchyTrees.Add(objHTree);
}
}
}
foreach (HierarchyTrees.HTree hTree in hierarchyTrees)
{
HierarchyTrees.HTree parentNode = hierarchyTrees.Find
(delegate(HierarchyTrees.HTree emp)
{ return emp.NodeID == hTree.UnderParent; });
if (parentNode != null)
{
foreach (TreeNode tn in tvHierarchyView.Nodes)
{
if (tn.Value == parentNode.NodeID.ToString())
{
tn.ChildNodes.Add(new TreeNode
(hTree.NodeDescription.ToString(), hTree.NodeID.ToString()));
}
if (tn.ChildNodes.Count > 0)
{
foreach (TreeNode ctn in tn.ChildNodes)
{
RecursiveChild(ctn, parentNode.NodeID.ToString(), hTree);
}
}
}
}
else
{
tvHierarchyView.Nodes.Add(new TreeNode
(hTree.NodeDescription, hTree.NodeID.ToString()));
}
}
tvHierarchyView.ExpandAll();
}
Create recursive function to traverse through hierarchical tree data structure. This functionality is developed using ASP.NET 2.0 and the recursive function can be avoided using CSharp .NET 3.5 using LINQ. Using anonymous delegate, we can compare the collection objects with some logical condition. Once the result set is filtered, it can be traversed and can be added as object item to tree view control. Create HierarchyTrees generic collection which contains Htree objects.
public void RecursiveChild
(TreeNode tn, string searchValue, HierarchyTrees.HTree hTree)
{
if (tn.Value == searchValue)
{
tn.ChildNodes.Add(new TreeNode
(hTree.NodeDescription.ToString(), hTree.NodeID.ToString()));
}
if (tn.ChildNodes.Count > 0)
{
foreach (TreeNode ctn in tn.ChildNodes)
{
RecursiveChild(ctn, searchValue,hTree);
}
}
}
Any ideas, corrections, and suggestions are most welcome.
The below reference is for Winform treeview control and I wrote the above article to make it available for ASP.NET treeview control as well. The important difference between winform and ASP.NET treeview control is FindNode.
In winform treeview control, we have tvHierarchyView.Nodes.Find where it finds a given node criteria and helps us add Htree object item at a given node value and hence one can use LINQ and can get rid of recursive function.
Unlike Winform, ASP.NET treeview control exposes tvHierarchyView.FindNode(XML Address path) which is more applicable for XML data type and hence not much of help.
