Table of Contents

At a glance
Licensing
Installation and deployment
DNN
New to Telerik RadTreeView?
Already using the control
Standards Compliance
AJAX Support
Feature OverView
How RadTreeView compares to ASP.NET Treeview
Getting Started
ASP.NET 2.0 Features
Templates
Defining TreeView Structure
Data Binding
Controlling the visual appearance
Context Menus
Custom Attributes
Using Checkboxes
Using the Drag and Drop Functionality
Load On Demand Support
Example scenarios (How to)
Telerik RadTreeView Client-Side
Telerik RadTreeView Server-Side
Interoperability with Other Controls
TroubleShooting
- Optimizing treeview performance
- NodeClick event is not fired
- Wrapping TreeNodes' text
- SelectedNode is empty
- The state is not persisted after URL navigation
- Secure Warnings
- The PostBack property can NOT be set declaratively in the aspx page
- Templates in my Telerik RadTreeView are not correctly positioned - they appear on the next line
- The DataItem property is empty
- Java script errors - 'RadTreeview' is undefined
- The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>)
- ImageUrl does not work
- Horizontal scrollbar does not appear
- Getting the NavigateUrl on the client-side
- Editing TreeNodes' Text when using templates
- Integration
API Reference
Get more help

NodeClick event is not fired		Send comments on this topic.
See Also

TroubleShooting > NodeClick event is not fired

Glossary Item Box

There are several reasons for the NodeClick event not to be fired.

The RadTreeView instance is not marked with AutoPostBack="True" - the AutoPostBack property should be enabled so that the treeview control fires a postback upon clicking a node. Since the NodeClick event is a server-side event, the treeview needs to fire a postback so that the NodeClick event gets executed. If you need to fire the NodeClick event only for certain nodes, you can mark only these nodes with PostBack="True".
The TreeNodes are marked with NavigateUrl - if the NavigateUrl property is set, clicking a node will cause another page to be opened either in a new or the same window. Hence, the NodeClick event cannot be fired as there has been a page redirection.

The TreeNodes are loaded on demand via a ServerSideCallback - When you add TreeNodes on the client-side (via ExpandMode.ServerSideCallBack), you should take into account that these nodes are not persisted at the server-side. Therefore, these nodes cannot take part in any server-side events. In other words, the NodeClick event will not be fired with these nodes.

Also, you cannot access the nodes on the server-side and change their properties. The nodes are accessible only on the client-side and can take part only in client-side events.

If you need to persist the expanded state of the TreeNodes after a postback, you can use the approach described in the following article:

Storing the expanded state of TreeNodes added via callback

If you need to access the nodes on the server-side, then you should definitely use ExpandMode.ServerSide. Furthermore, you can wrap the treeview with an AJAX Panel (Telerik RadAjaxPanel) that will transform each postback into a callback. Thus, you will keep the needed client-side behavior.

Note: RadTreeView for ASP.NET AJAX, formerly known as "Prometheus", does not have this limitation. Nodes added via ServerSideCallBack persist their state on the server and fire their server-side events. Please check out the online example demonstrating this: Client-Side Load-On-Demand.

RadTreeView for ASP.NET

See Also