The field in a CDT used as an automatically generated primary key should be which data type?

When defining a Custom Data Type (CDT) in Appian, it is important for the field designated as the automatically generated primary key to be a Number (Integer) data type. The primary key must be a unique identifier for each record in the database, and using a Number (Integer) enhances efficiency, particularly in terms of indexing and performance.

Integer types are well-suited for primary keys because they can be easily sorted and compared, which is essential for maintaining the integrity of the data. Additionally, many database systems optimize storage and retrieval of integer values, which can lead to better query performance. Furthermore, primary keys are often auto-incremented in relational databases, and integer data types align well with this feature, allowing for seamless record generation without manual input.

Text, Date/Time, and Boolean types do not fulfill the requirements as effectively. Text can lead to larger storage requirements, complicating indexing and comparisons. Date/Time may introduce complexity due to varying formats and possible null values. Boolean values only represent two states, which do not provide the uniqueness needed for primary key identification in most scenarios. Thus, the Number (Integer) data type is optimal for an automatically generated primary key in a CDT.