|
|
|
|
How data mappings are deployed to CDD tables
When you create a deployment package and choose one or more data mappings to create CDD data mappings:
- Each data set becomes a target table, and each data series becomes a column in the table.
- The key columns of the target tables are defined by the value of the Target Key Type CDD custom property on the data set.
- Additional attributes of the target tables and columns are defined by the values of CDD custom properties on the item, data set, and data series.
- When you map an item with a unit into a text data series, you must choose whether to map the entered value, normalized value, or entered unit. However, all items are mapped as the entered value regardless of what is specified when the item is mapped. InForm CDD supports the mapping of the different parts, but there is no option in InForm to choose the column names or which parts to include, so the CDD data mapping from data mapping definitions ignores this setting.
- All values in a multi-select codelist are mapped to a single column. It is not possible to define a data series mapping in such a way that each possible value of a multi-select codelist appears in a different CDD table column.
- When you define a data set, you can specify one or more standard data dimensions and custom data dimensions. Standard and custom data dimensions are not used in CDD data mappings.
- You can define CDD data mappings for associations by associating two forms and selecting those forms as the value of the Associated Forms property on a data set.
