When you add a datafunnel to a project, CenterView Builder encapsulates it within a Data-Source object. The data-source object is unique to each data recipient (table or Corda Image); the datafunnel can be referenced by multiple data recipients. The data-source object makes it possible to manipulate datafunnel output for a specific presentation without affecting other data recipients that may be utilizing the same datafunnel. For more information on data manipulation and transformation, see Data Transformation.
The data-source object also provides a data-type attribute that lets you identify how data is organized in the data set. The following table lists the supported values for data-type.
| Data Type | Description | Object Types |
|---|---|---|
| legacy | Data series are in rows and data categories are in columns. This is a legacy PopChart data format. | All Graphs |
| item-value | Data is stored primarily in two columns: Column 1 contains item names, and column 2 contains values. Columns 3 and higher are available for meta data related to drilldown and pop-up. | Bar, pie, pareto, line, step, radar, heat-map |
| group-item-value | Data is stored primarily in three columns: Column 1 contains group names, column 2 contains item names, and column 3 contains values. Columns 4 and higher are available for meta data related to drilldown and pop-up. | Bar, stacked bar, pareto, line, step, radar, heat-map, line-bar combo, stacked line-bar combo |
| line-xy | Data is stored primarily in three columns: Column 1 contains line names, column 2 contains X values, and column 3 contains Y values. Columns 4 and higher are available for meta data related to drilldown and pop-up. | XY Line, XY Scatter |
| line-xybubble | Data is stored primarily in four columns: Column 1 contains line names, column 2 contains X values, column 3 contains Y values, and column 4 contains Bubble values. Columns 5 and higher are available for meta data related to drilldown and pop-up. | XY Bubble, XY Combo, XY Combo Dual Y |
| line-timey | Data is stored primarily in three columns: Column 1 contains line names, column 2 contains Time values, and column 3 contains Y values. Columns 4 and higher are available for meta data related to drilldown and pop-up. | TimeY Line, TimeY Scatter |
| line-timeybubble | Data is stored primarily in four columns: Column 1 contains line names, column 2 contains Time values, column 3 contains Y values, and column 4 contains Bubble values. Columns 5 and higher are available for meta data related to drilldown and pop-up. | TimeY Bubble, TimeY Combo, TimeY Combo Dual Y |
| stock-hl | Data is stored primarily in three columns: Column 1 contains date and/or time, column 2 contains high values, and column 3 contains low values. Columns 4 and higher are available for meta data related to drilldown and pop-up. | Stock HighLow |
| stock-hloc | Data is stored primarily in five columns: Column 1 contains date and/or time, column 2 contains high values, column 3 contains low values, column 4 contains open values, and column 5 contains close values. Columns 6 and higher are available for meta data related to drilldown and pop-up. | Stock HLOC, Candlestick |
| boxplot | Data is stored primarily in six columns: Column 1 contains item names, column 2 contains low values, column 3 contains Q1 values, column 4 contains median values, column 5 contains Q3 values, and column 6 contains high values. Columns 7 and higher are available for meta data related to drilldown and pop-up. | Box-plot |
| boxplot-outliers | Data is stored primarily in six columns: Column 1 contains item names, column 2 contains low values, column 3 contains Q1 values, column 4 contains median values, column 5 contains Q3 values, and column 6 contains high values. Columns 7 and higher contain outliers. | Box-plot with Outliers |
| map-data | Data is stored primarily in 2 columns: Column 1 contains point names, column 2 contains point values. Columns 3 and higher are available for meta data related to drill down and popup. This is used for setting values on existing data points. | Maps |
| map-data-lat-long | Data is stored primarily in 4 columns: Column 1 contains point names, column 2 contains point values, column 3 contains the latitude value for the point, column 4 contains the longitude value for the point. Columns 5 and higher are available for meta data related to drill down and popup. This is used for adding new data points to a map. | Maps |
The following tables provide samples of well-formed data tables for each supported data-type value.
legacy
This parameter value causes data-source to treat incoming data as if it were in the legacy, untyped format.
item-value
When DataType = item-value, data tables should be organized as in the following example:
| Item | Value | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|
| 1 | 100 | www.corda.com | myHoverText | Other Text |
| 2 | 200 | |||
| 3 | 300 |
group-item-value
When DataType = group-item-value, data tables should be organized as in the following example:
| Group | Item | Value | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|
| 1 | 1 | 100 | www.corda.com | myHoverText | Other Text |
| 1 | 2 | 200 | |||
| 1 | 3 | 300 | |||
| 2 | 1 | 400 | |||
| 2 | 2 | 500 | |||
| 2 | 3 | 600 | |||
| 3 | 1 | 700 | |||
| 3 | 2 | 800 | |||
| 3 | 3 | 900 |
line-xy
When DataType = line-xy, data tables should be organized as in the following example:
| Item | X | Y | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|
| 1 | 1 | 2 | www.corda.com | myHoverText | Other Text |
| 1 | 3 | 4 | |||
| 1 | 5 | 6 | |||
| 2 | 7 | 8 | |||
| 2 | 9 | 10 | |||
| 2 | 11 | 12 | |||
| 3 | 13 | 14 | |||
| 3 | 15 | 16 | |||
| 3 | 17 | 18 |
line-xybubble
When DataType = line-xybubble, data tables should be organized as in the following example:
| Item | X | Y | Bubble | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|---|
| 1 | 1 | 2 | 3 | www.corda.com | myHoverText | Other Text |
| 1 | 4 | 5 | 6 | |||
| 1 | 7 | 8 | 9 | |||
| 2 | 7 | 8 | ||||
| 2 | 9 | 10 | ||||
| 2 | 11 | 12 | ||||
| 3 | 13 | 14 | ||||
| 3 | 15 | 16 | ||||
| 3 | 17 | 18 |
line-timey
When DataType = line-timey, data tables should be organized as in the following example:
| Item | Time | Y | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|
| 1 | 1/22/00 | 1 | www.corda.com | myHoverText | Other Text |
| 1 | 2/22/00 | 2 | |||
| 1 | 3/22/00 | 3 | |||
| 2 | 1/22/00 | 4 | |||
| 2 | 2/22/00 | 5 | |||
| 2 | 3/22/00 | 6 | |||
| 3 | 1/22/00 | 7 | |||
| 3 | 2/22/00 | 8 | |||
| 3 | 3/22/00 | 9 |
line-timeybubble
When DataType = line-timeybubble, data tables should be organized as in the following example:
| Item | Time | Y | Bubble | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|---|
| 1 | 1/22/00 | 1 | 1 | www.corda.com | myHoverText | Other Text |
| 1 | 2/22/00 | 2 | 2 | |||
| 1 | 3/22/00 | 3 | 3 | |||
| 2 | 1/22/00 | 4 | 4 | |||
| 2 | 2/22/00 | 5 | 5 | |||
| 2 | 3/22/00 | 6 | 6 | |||
| 3 | 1/22/00 | 7 | 7 | |||
| 3 | 2/22/00 | 8 | 8 | |||
| 3 | 3/22/00 | 9 | 9 |
stock-hl
When DataType = stock-hl, data tables should be organized as in the following example:
| Item | High | Low | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|
| 1 | 3 | 2 | www.corda.com | myHoverText | Other Text |
| 2 | 9 | 7 | |||
| 3 | 5 | 1 |
stock-hloc
When DataType = stock-hloc, data tables should be organized as in the following example:
| Item | High | Low | Open | Close | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|---|---|
| 1 | 9 | 1 | 5 | 7 | www.corda.com | myHoverText | Other Text |
| 2 | 8 | 2 | 5 | 5 | |||
| 3 | 7 | 3 | 7 | 5 |
boxplot
When DataType = boxplot, data tables should be organized as in the following example:
| Item | Low | Q1 | Median | Q3 | High | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|---|---|---|
| 1 | 1 | 2 | 3 | 4 | 5 | www.corda.com | myHoverText | Other Text |
| 2 | 2 | 3 | 4 | 5 | 6 | |||
| 3 | 3 | 4 | 5 | 6 | 7 |
boxplot-outliers
When DataType = boxplot-outliers, data tables should be organized as in the following example:
| Item | Low | Q1 | Median | Q3 | High | Outlier1 | Outlier2 |
|---|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 11 | |
| 2 | 3 | 4 | 5 | 6 | 7 | ||
| 3 | 4 | 5 | 6 | 7 | 8 | 1 | 14 |
map-data
When DataType = map-data, data tables should be organized as in the following example:
| Point Name | Value | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|
| point1 | 2 | www.corda.com | myHoverText | Other Text |
| point2 | 7 | www.corda.com | myHoverText | Other Text |
| point3 | 1 | www.corda.com | myHoverText | Other Text |
map-data-lat-long
When DataType = map-data-lat-long, data tables should be organized as in the following example:
| Point Name | Value | Latitude | Longitude | Meta-data1 | Meta-data2 | Meta-data3 |
|---|---|---|---|---|---|---|
| point1 | 1 | 40.34 | -111.72 | www.corda.com | myHoverText | Other Text |
| point2 | 2 | 37.41 | -79.14 | www.corda.com | myHoverText | Other Text |
| point3 | 3 | -23.46 | -46.53 | www.corda.com | myHoverText | Other Text |