What is the impact of reordering fields in a record type backed by a database table?

What is the impact of reordering fields in a record type backed by a database table?

• A. There is no impact from the change.
• B. It changes the underlying database schema.
• C. It requires a data migration.
• D. It affects data retention.

Answer: (A)

Understanding how a record type maps to storage is key here. When a record type is backed by a database table, each field in the record corresponds to a specific column in the table. Reordering the fields in the record type does not change which columns exist or how data is stored; it only changes the order in which those fields are presented or arranged in the Appian UI. The actual data, the table structure, and the relationships remain the same, so no data migration is needed and the database schema is unaffected. This is why reordering has no impact beyond presentation.

Understanding how a record type maps to storage is key here. When a record type is backed by a database table, each field in the record corresponds to a specific column in the table. Reordering the fields in the record type does not change which columns exist or how data is stored; it only changes the order in which those fields are presented or arranged in the Appian UI. The actual data, the table structure, and the relationships remain the same, so no data migration is needed and the database schema is unaffected. This is why reordering has no impact beyond presentation.