What is required to define a new Primary Key in a CDT?

To define a new Primary Key in a Complex Data Type (CDT) in Appian, it is essential to utilize a unique field. The primary key serves as a unique identifier for each instance of the CDT, ensuring that each record can be distinctly accessed and manipulated within the system.

By selecting a unique field, you guarantee that no two records will share the same value for this field, which is fundamental for maintaining data integrity. The unique field must not have duplicate values across the instances of the CDT, allowing for reliable data management and retrieval operations.

Using multiple fields or an array of fields could potentially indicate that more than one piece of data is required to uniquely identify a record, which can complicate data management and is not the straightforward approach Appian utilizes when defining primary keys. Selecting any field is also not suitable because it does not ensure uniqueness, which is critical for primary keys. Thus, using a unique field is the proper method for setting up a primary key in a CDT.