Show TOC

# Charts Used in Overview Pages

This section describes the type of analytic chart cards that can be used in overview pages. They can be line, bubble, donut, column, stacked column, vertical bullet, combination, or scatter.

Line Chart
A line chart displays information as a series of data points connected by straight line segments. They are often used to visualize a trend in data over time. Line charts require at least one measure and one dimension.
• Dimensions for which the role is set to category, makes up the x-axis (category axis). If no dimension is specified with this role, the first dimension is used as the x-axis. It's recommended to use only time-based dimensions (for example, day, date, week, month, quarter, or year) for the category axis of a line chart.
• Dimensions for which the role is set to series make up the line segments of the chart, with different colors assigned to each dimension value. If multiple dimensions are assigned this role, the values of all such dimensions together are considered as one dimension and a color is assigned.
• Measures make up the y- axis (value axis). If there are multiple measures, then each measure is represented by a different colored line inside the chart area.
Bubble Chart
Bubble charts display up to three measures and two dimensions of data. The three measures are reflected in the x- and y- axis, and in the size of the bubbles. The dimensions can be expressed in the colors and/or shapes of the bubbles. Bubble charts require three measures and at least one dimension, yet allow a maximum of two.
• The first measure for which the role is set to axis1, or if none exists, the first measure for which the role is set to axis2, or if none exists, the first measure for which the role is set to axis3, is assigned to the feed UID valueAxis. This makes up the X axis.
• The first measure for which the role is set to axis2, or the second measure for which the role is set to axis1 (if role axis2 does not exist for the first measure), or the first measure for which the role is set to axis3 (if role axis1 does not exist for the second measure), is assigned to the feed UID valueAxis2. This makes up the Y axis.
• The remaining measure is assigned to feed UID bubbleWidth. This determines the size of the bubble.
• The dimensions for which the role is set to series are assigned to the feed UID color. Different values for this dimension in the data set result in different colored data points in the chart. If multiples dimensions are set with the category role, only the first dimension is considered. If both dimensions have been assigned the role series then each combination of the dimension member will get a unique color.
For example, if "Year" and "Country" are the dimensions and both have been assigned the role series then "India/2015", "India/2016", "Germany/2015", "Germany/2016" will be represented as a different colored bubble. If a dimension is not marked with any role, then the dimension members will get the same color. In the above example, if year is not marked with any color, then the bubbles will only have two colors - one for all records of India and one for all records of Germany, irrespective of the year.
Note Assigning the role of a dimension as category would lead to different shaped data points for different values of the dimension. However, this is not recommended for a bubble chart card. Configuring the role of a bubble chart dimension as category is discouraged
• The dimensions for which the role is set to category are assigned to the feed UID shape. Different values for this dimension in the data set result in different shaped data points in the chart. If multiples dimensions are set with the category role, only the first dimension is considered.
Following is a code snippet which demonstrates defining a bubble chart card. Note that there are three measures (under the MeasureAttributes property) and one dimension (under the DimensionAttributes property).

Example

Sample Code
```<Annotation Term="UI.Chart" Qualifier="Qualifier_ID_1">
<Record Type="UI.ChartDefinitionType">
<PropertyValue Property="Title" String="View1" />
<PropertyValue Property="ChartType" EnumMember="UI.ChartType/Bubble"/>
<PropertyValue Property="MeasureAttributes">
<Collection>
<Record Type="UI.ChartMeasureAttributeType">
<PropertyValue Property="Measure" PropertyPath="SalesShare" />
<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis1" />
</Record>
<Record Type="UI.ChartMeasureAttributeType">
<PropertyValue Property="Measure" PropertyPath="TotalSales" />
<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis2" />
</Record>
<Record Type="UI.ChartMeasureAttributeType">
<PropertyValue Property="Measure" PropertyPath="Sales" />
<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis3" />
</Record>
</Collection>
</PropertyValue>
<PropertyValue Property="DimensionAttributes">
<Collection>
<Record Type="UI.ChartDimensionAttributeType">
<PropertyValue Property="Dimension" PropertyPath="Product" />
<PropertyValue Property="Role" EnumMember="UI.ChartDimensionRoleType/Series" />
</Record>
</Collection>
</PropertyValue>
</Record>
</Annotation>
```
Example of Line and Bubble Chart Cards
 Line Chart Card Bubble Chart Card
Note Analytic cards don't have a fixed height. The height is adjusted automatically to accomodate the data points and legends. Legends are created automatically based on the defined measures and dimensions.
Donut Chart

A donut chart displays data as different colored sections of a donut. The value of the measure determines the size of each section. Donut charts help the viewer to quickly determine the key area that needs attention.

Donut charts require exactly one measure. You can provide more than one dimension, in which case they are stacked so that the sections of the chart represent the combination of both dimensions. For example, if you define "Sales" as your measure, and provide two dimensions: "Year" and "Country", the chart will display the sales data of each combination of year and country as a separate colored section.

Column Chart

A column chart displays data, such as total product sales over a period of years. The number of columns is equal to the number of measures in the annotation file.

Column charts require at least one measure and one dimension. Irrespective of the role defined for the measure in the annotation file, every measure will be represented as a separate column. Similarly, irrespective of the role defined in the annotation file, every dimension will be added to the category axis (x-axis).

Example of Donut and Column Chart Cards
 Donut Chart Card Column Chart Card
Note Analytic cards don't have a fixed height. The height is adjusted automatically to accomodate the data points and legends. Legends are created automatically based on the defined measures and dimensions.
Stacked Column Chart

A stacked column chart is similar to the column chart; however, all measures irrespective of role, get stacked on top of each other. There should be at least one dimension with the assigned role category and all dimensions with this role would be added to the category axis (x-axis). All dimensions with role series also get stacked. It's recommended to either stack based on dimensions or measures, but not mix both in a single chart card.

Vertical Bullet Chart

axis. All measures with role axis1 would be represented as solid colored columns, which represent actual values. All measures with role axis2 would be represented as a solid black line, which represents the target value.

Example of Stacked Column and Vertical Bullet Chart Cards
 Stacked Colulmn Chart Card Vertical Bullet Chart Card
Note Analytic cards don't have a fixed height. The height is adjusted automatically to accomodate the data points and legends. Legends are created automatically based on the defined measures and dimensions.
Combination Chart

Vertical bullet charts accept at least one measure and one dimension. All dimensionsWith a combination chart card, you can display more than one measure; the first measure gets displayed in a column format and theVertical bullet charts accept at least one measure and one dimension. All dimensions subsequent measure is displayed as a line within the chart. It's recommended to have irrespective of their role will be assigned to the category subsequent measure is displayed as a line within the chart. It's recommended to have irrespective of their role will be assigned to the category only one time-based dimension for the category axis in such charts. only one time-based dimension for the category axis in such charts.

All measures, irrespective of their roles, get assigned to the feed UID value axis. There must be at least two measures for combination chart cards to work. All dimensions with role "Category" get assigned to the category axis. This is also the default role. There must be at least one role that can be assigned to the category axis. All dimensions with role "Series" get assigned to feed UID color and get displayed within the chart area with different colored column and line combination for each of its members.

Example

Sample Code
```<Annotation Term="UI.Chart" Qualifier="Eval_by_Currency_Combination">
<Record Type="UI.ChartDefinitionType">
<PropertyValue Property="Title" String="Sales and Total Sales" />
<PropertyValue Property="ChartType" EnumMember="UI.ChartType/Combination"/>
<PropertyValue Property="MeasureAttributes">
<Collection>
<Record Type="UI.ChartMeasureAttributeType">
<PropertyValue Property="Measure" PropertyPath="sales" />
<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis1" />
</Record>
<Record Type="UI.ChartMeasureAttributeType">
<PropertyValue Property="Measure" PropertyPath="totalsales" />
<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis1" />
</Record>
</Collection>
</PropertyValue>
<PropertyValue Property="DimensionAttributes">
<Collection>
<Record Type="UI.ChartDimensionAttributeType">
<PropertyValue Property="Dimension" PropertyPath="quarter_1" />
<PropertyValue Property="Role" EnumMember="UI.ChartDimensionRoleType/Category" />
</Record>
</Collection>
</PropertyValue>
</Record>
</Annotation>```

Scatter Chart

With a scatter chart card, you can visualize the distribution of data points over two measures; it requires exactly two measures and at least one dimension. The first measure for which the role is set, is set to axis1, or if none exists, is set to axis2, or if none exists, the first measure for which the role is set, is set to to axis3, is assigned to the feed UID valueAxis. This makes up the x- axis. The other measure is plotted on the y-axis.

A scatter chart card supports a maximum of two dimensions. If the dimension is not marked with any role, then all members of the dimension are plotted as same colored equal sized bubbles in the chart. A maximum of one dimension can be marked with role "Series" and all members of such a dimension get a different color. A maximum of one dimension can be marked with role "Category" and all members of such a dimension get a different shape.

Example

Sample Code
```<Annotation Term="UI.Chart" Qualifier="Eval_by_Currency_Scatter">
<Record Type="UI.ChartDefinitionType">
<PropertyValue Property="Title" String="Scatter Chart no role" />
<PropertyValue Property="ChartType" EnumMember="UI.ChartType/Scatter" />
<PropertyValue Property="MeasureAttributes">
<Collection>
<Record Type="UI.ChartMeasureAttributeType">
<PropertyValue Property="Measure" PropertyPath="salesshare" />
<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis1" />
</Record>
<Record Type="UI.ChartMeasureAttributeType">
<PropertyValue Property="Measure" PropertyPath="totalsales" />
<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis2" />
</Record>
</Collection>
</PropertyValue>
<PropertyValue Property="DimensionAttributes">
<Collection>
<Record Type="UI.ChartDimensionAttributeType">
<PropertyValue Property="Dimension" PropertyPath="suppliercompany" />
</Record>
</Collection>
</PropertyValue>
</Record>
</Annotation>```
Example Combination and Scatter Chart Cards
 Combination Chart Card Scatter Chart Card
Note Analytic cards don't have a fixed height. The height is adjusted automatically to accomodate the data points and legends. Legends are created automatically based on the defined measures and dimensions.