The Web Dashboard is a client-side control which communicates with server part using HTTP requests:
The client communicates with the server part using a RESTful API, allowing to you send multiple data requests simultaneously. For example, if you change the master filter in a dashboard containing several detail items, all these items send their queries to the server. These requests are independently processed on the server side for better performance.
A combined application comprises client and server parts in one application. The following frameworks-based wrappers for the DashboardControl are available when creating a Web Dashboard application:
Separated client and server parts allow you to use Web Dashboard in the following ways:
Separated client and server parts require configuring one Web Dashboard application as a server and configuring another Web Dashboard application as a client to enable working with the server.
The table below illustrates correlations between server and client. The column headers display platforms you can use as a server, the row headers show available client counterparts.
Client \ Server
ASP.NET HTTP Handlers
ASP.NET Web Forms (UseDashboardConfigurator = false)1
ASP.NET Web Forms (UseDashboardConfigurator = true)
1 It is a default ASPxDashboardControl mode. See Server-Side API Overview to learn more.
2 In this case, the Web Forms Dashboard sends requests only to its own instance.
Note that you need to set up cross-origin resource sharing (CORS) on your back-end to configure corresponding permissions to access selected resources from a server at a different origin.
Web Dashboard needs a server-side background to operate with data, store dashboards, etc. You need to configure some specific settings before the first use:
The Web Dashboard requires creating a special dashboard storage to keep the dashboards. End-users can save new dashboards to this storage and open existing dashboards. The following storage types are available:
See the Preparing a Dashboard Storage topics in the required framework's section (for instance, ASP.NET Web Forms Dashboard Control - Preparing a Dashboard Storage).
Use the following approaches to supply the Web Dashboard with data:
The Web Dashboard can act as the Designer or Viewer. You can set the default working mode on a server side, or switch between the Designer and Viewer using the client-side API. See the Designer and Viewer Modes topics for a required framework's section (for instance, Designer and Viewer Modes).