Can entity identifiers in OutSystems be composite keys?

In OutSystems, entity identifiers are required to be unique and are typically defined as single primary keys. The platform does not support the concept of composite keys, which are combinations of two or more attributes that together uniquely identify a record in a database. Instead, each entity must have a single identifier that is used to ensure data integrity and facilitate operations like CRUD (Create, Read, Update, Delete) on the records.

The design philosophy of OutSystems emphasizes simplicity and speed in application development, which is why it standardizes the use of single primary keys rather than allowing more complex key structures like composite keys. This design choice helps streamline database interactions and reduces the complexity associated with handling multiple key components when performing operations.

While there might be workarounds or specific implementations that could give the illusion of composite behavior, the core framework itself is fundamentally built around the use of single attributes as identifiers, affirming the stance that entity identifiers cannot be composite keys.