Data Binding Overview
The Telerik UI for ASP.NET Core OrgChart provides flexible data binding capabilities that allow you to visualize hierarchical organizational structures from various data sources. You can choose the appropriate binding method based on your application architecture and data requirements.
The default casing for JSON strings in ASP.NET Core is camelCase. The Telerik UI components that are data-bound depend on PascalCase formatted response from the server. If the JSON serialization isn't configured properly, the UI components will display wrong data. To find out how to configure the application to return the data in Pascal-case, refer to the JSON Serialization article.
Data Binding Approaches
The OrgChart supports the following data binding methods:
Local Data Binding
Bind the OrgChart to a local dataset by setting the data using a client-side logic after the component initialization. This approach is optimal for:
- Small to medium-sized organizational structures that can be loaded in memory.
- Static hierarchical data that does not require updates.
- Scenarios where all organizational data is available at render time.
For detailed implementation instructions, see Local Data Binding documentation.
Remote Data Binding
Connect the OrgChart to a remote endpoint using AJAX operations. This enables:
- Dynamic loading of large organizational structures.
- Real-time data updates from external sources.
- Improved performance with large datasets through on-demand data loading.
For more information and examples, refer to the Remote Data Binding documentation.
Data Binding in Razor Pages
You can seamlessly integrate the OrgChart component into Razor Pages applications. All the data binding approaches described above can be configured within Razor Pages scenarios.
The component supports both HtmlHelper and TagHelper syntax, and allows you to send the anti-forgery token when connecting to remote endpoints to ensure secure data operations.
For detailed implementation instructions, refer to the OrgChart in Razor Pages article.
Key Considerations
When selecting a data binding approach for the OrgChart, evaluate the following factors:
- Performance—Local binding offers faster initial rendering, while remote binding provides better performance with large datasets.
- Data volume—Large organizational structures are better handled with remote binding and enabled on-demand loading.
- Security—Remote binding provides better control over data access through server-side validation and authorization.
- Real-time requirements—Remote binding is essential for scenarios requiring live data updates and dynamic content refresh.
- Maintenance—Local binding is simpler for static data, while remote binding offers more flexibility for evolving data requirements.