This page was last edited on June 22, 2022, at 22:16.
Comments or questions about this documentation? Contact us for support!
In the Column List:
Modified: 8.5.014.34 (in Microsoft SQL Server, data type for the RECORD_FIELD_1_STRING_1 Through RECORD_FIELD_1_STRING_10 columns modified in single-language databases); 8.5.003 (in Oracle, fields with VARCHAR data types use explicit CHAR character-length semantics)
In partitioned databases, this table is not partitioned.
This table allows contact attempt facts to be described by deployment-specific field values of outbound campaign calling lists. Each row describes a distinct combination of calling list field values. A new row is issued for each distinct combination of calling list field values that are encountered in the contact attempt source data. Calling list field values must be of low cardinality, to prevent this dimension from becoming as large as the fact tables.
Column | Data Type | P | M | F | DV |
---|---|---|---|---|---|
RECORD_FIELD_GROUP_1_KEY | int | X | X | ||
TENANT_KEY | int | X | X | ||
CREATE_AUDIT_KEY | numeric(19) | X | X | ||
RECORD_FIELD_1_STRING_1 Through RECORD_FIELD_1_STRING_10 | nvarchar(255) | ||||
PURGE_FLAG | numeric(1) |
The primary key of this table and the surrogate key that is used to join this dimension table to the fact tables.
The surrogate key that is used to join the TENANT dimension to the fact tables.
The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools—that is, applications that need to identify newly added data.
Modified: 8.5.014.34 (in Microsoft SQL Server, data type changed from varchar to nvarchar in single-language databases)
The text string value number one through ten, respectively, of a custom record field.
No indexes are defined.