ASP.NET Core Diagram Overview

Telerik UI for ASP.NET Core Ninja image

The Diagram is part of Telerik UI for ASP.NET Core, a professional grade UI library with 110+ components for building modern and feature-rich applications. To try it out sign up for a free 30-day trial.

The Telerik UI Diagram TagHelper and HtmlHelper for ASP.NET Core are server-side wrappers for the Kendo UI Diagram widget.

The Diagram represents information in a schematic way and according to particular visualization techniques.

Basic Configuration

  1. Return the data as JSON.

    public ActionResult _OrgChart()
        return Json(DiagramDataRepository.OrgChart(), JsonRequestBehavior.AllowGet);
  2. In the view, configure the Diagram to use the action method that was created in the previous step.

            .DataSource(dataSource => dataSource
                .Read(read => read
                    .Action("_OrgChart", "Diagram") // Specify the action method and controller names.
                .Model(m => m.Children("Items"))
            .Layout(l => l.Type(DiagramLayoutType.Layered))
        <kendo-diagram name="diagram">
            <hierarchical-datasource server-operation="false">
                    <read url="@Url.Action("_OrgChart", "Diagram")" />
                    <hierarchical-model children="Items"></hierarchical-model>
            <editable enabled="false" />
            <layout type="DiagramLayoutType.Layered"></layout>

Functionality and Features


You can subscribe to all Diagram events. For a complete example on basic Diagram events, refer to the demo on using the events of the Diagram.

Referencing Existing Instances

To reference an existing Kendo UI Diagram instance, use the configuration option. Once a reference is established, use the Diagram client-side API to control its behavior.

    // Place the following after the Diagram for ASP.NET Core declaration.
        $(function() {
            // The Name() of the Diagram is used to get its client-side instance.
            var diagram = $("#diagram").data("kendoDiagram");

See Also

In this article