Blog: Posts from March, 2015

The “bar” chart type renders horizontal bars for each row of data. One use case would be to quickly compare records grouped by lookup values. For example, it can be used to show the number of orders made with each employee on the Orders page of the Northwind sample app. The chart reveals that “Peacock” is the most active employee.

To use “bar” chart type, add the keyword “bar” to any “pivot-” tag, and make sure that it is separated with hyphens (-).

Here is the data for the above graph:

Hovering over or clicking on a single bar will reveal the data behind that bar.

When multiple values are specified for each row, a bar will be rendered for each value in a different color.

Multiple columns of data can be seen in the table below.

Each row can also be displayed as a single bar, with values stacked on that bar, by using the “barstacked” chart type.

The “area” chart type is useful for showing change in a value over time. For example, it can show how the number of orders in the Northwind database changes by the order date. To use “area” chart type, add the keyword “area” to any “pivot-” tag, and make sure that it is separated with hyphens (-).

The data for the chart can be seen below.

Note that the chart above uses “-date” keyword. This keyword will direct the server to try several pivots with varying date group sizes and select the best fitting chart. An alternative definition to define a chart that looks exactly like the one above would look like the following:

Discrete points can be clicked on to reveal the row, column, and value for that data point.

This chart type is also effective for showing multiple values on the same chart.  The example chart below shows the frequency of orders made with each shipper over time. It uses order date for the rows, and the shipper company name (ShipVia) as the columns.

The data for the graph above can be seen here:

By default, the values are shown independently. You can choose to stack the values cumulatively by using the “areastacked” tag instead.