Data Sets Tags

The data-sets block lists the data sets that are used in the factory configuration. Within each data-set block you specify rules for that data set.

In the following example, the individual data set blocks are collapsed:

data-sets {
  data-set "Accounts" {
  data-set "Charges" {
  data-set "Payments" {
}

NOTE: In Workbench 7.1(13) and later, all Spectre Build input types (*-input) can be included in the data-set block. Operations, such as filter and limit-rows, are supported inside the input tag block. For the complete list of operational attributes, see General Build Tags, Text, cBase, and Dive Input Build Tags, and ODBC Input Build Tags. Data sets always begin with a single table of data.

Data Sets Tags

Tags	Examples	Notes
data-sets	data-sets { data-set "Accounts" { ... } data-set "Charges" { ... } ... }	Defines the container tag for `data-set` tags.
data-set	data-set "Accounts" { ... }	Code block that names the data set and starts the sub-block. NOTE: Each data set defined in the data-sets block must be used in at least one scope defined within the scopes block for the factory to process properly.
file	data-set "Accounts" file="data-sets/Accounts.factory-data-set"	Supporting tag for `data-set` when using separate factory-data-set files along with the main cfg.factory. See Multiple Configuration Files.
cbase-input	cbase-input "/cbases/accounts.cbase"	Sub-tag for `data-set` that specifies the location of the cBase that provides input for the data set. Additional operations are supported.
dive-input	dive-input "/programs/Profit.dive"	Sub-tag for `data-set` that specifies the location of the Spectre Dive that provides input for the data set. Additional operations are supported.
odbc-input	odbc-input query-path="/programs/inventory.sql"	Sub-tag for `data-set` that specifies the location of the ODBC input for the data set. Additional operations are supported.
plugin	plugin "Build" { dimension "Color" plugin-rule "Letter" }	Sub-tag for `data-set` that specifies the factory plugin (Build in this example) that provides input for the data set. Here the output column Letter is defined as a `plugin-rule` in the data set. See Factory Plugin Configuration File Tags.
plugin-input	plugin-input "Plugin Name" { ... }	Sub-tag for `data-set` that specifies a factory plugin as the source of the data. The data set will start with the rules specified in the `plugin-input`. With this feature, some operations that needed to be done in ETL before the factory was built can now be incorporated into the factory itself. See Plugin Versus Plugin-Input.
plugin-rule	plugin-input "Generate" { plugin-rule "Color" plugin-rule "Mood" } plugin "Concat" { dimension "Key" plugin-rule "Revenue Desc" }	Sub tab for `plugin-input` and `plugin` that names the rule that corresponds to the column output by the named plugin (Generate and Concat in these examples).
text-input	text-input "/data/daily transactions.txt"	Sub-tag for `data-set` that specifies the location of the text file that provides input for the data set. Additional operations are supported.
tunnel-input	tunnel-input "/programs/todays-data.tnl"	Sub-tag for `data-set` that specifies the location of the Tunnel input included in the data set.
shift-current-date	shift-current-date	Shifts the current date forward by one day for any calculations on this data set, overriding the `default-current-date` tag in the factory configuration file. This tag is intended for data sets that are updated throughout the day—for example, hourly.
<rules>	data-set "Account"{ cbase-input /cbases/accounts.cbase" <calc-rules> <flag rules> <lookup rules> <plugin rules> <source rules> }	Sub-tags for `data-set` that describes each rule for the data set. For more information, see Rules Tags.