Which is true about primary keys in OutSystems?

The accurate statement about primary keys in OutSystems is that they can be simple or composite. A simple primary key consists of a single attribute that uniquely identifies a record in the database, whereas a composite key is formed by combining two or more attributes to create a unique identifier for records. This versatility allows developers to design their database schema effectively, accommodating various data modeling requirements.

In OutSystems, primary keys serve as unique identifiers for entities, ensuring that each record can be accurately retrieved and manipulated. The ability to use either simple or composite keys is crucial in maintaining data integrity and supporting complex relationships within the data model.

The assertion that only simple keys are supported is incorrect because it overlooks the functionality provided by OutSystems to create more complex keys that suit different database schemas. Additionally, primary keys in OutSystems must indeed be unique identifiers; however, this does not negate the possibility of defining them as either simple or composite. Therefore, understanding the properties and capabilities of primary keys is essential for effective database design in OutSystems applications.