Relational Tables (RTs) in Acoustic Campaign are designed to maintain data integrity and ensure accurate record matching. There are important limitations and best practices to understand when working with unique identifiers and key structures.

Editing the unique identifier of an existing relational table

You cannot modify the unique identifier of an existing Relational Table. This restriction is by design and prevents data corruption, duplicate records, and mismatches between related data.

How to change the unique identifier

If you need a different unique identifier, you must recreate the table:

1. Create a new Relational Table with the correct unique identifier.
2. Import or migrate your data into the new table.
3. Delete the old Relational Table if it is no longer required.

Creating composite keys in relational tables

Although a Relational Table can have only one unique identifier field, you can effectively use a composite key by mapping multiple columns when linking the RT to your database.

How composite keys work

• During database-to-RT mapping, select multiple columns.
• These columns are treated together as a composite key during data retrieval.
• Records are uniquely identified using the combined field values.

This approach allows more flexible data relationships without changing the RT's single unique identifier constraint.

Important considerations

• Only one field can be marked as the unique identifier within the Relational Table configuration.
• Composite key behavior is achieved through database mapping, not through RT settings.
• Changing the key structure later requires recreating the Relational Table.

Best practice

Before creating a Relational Table, carefully plan which field — or combination of fields — will uniquely identify your records. Proper planning helps avoid unnecessary table recreation and ensures long-term data consistency.