If you need to rename a field in a Custom Data Type (CDT) that is backed by a database entity, and the data store's Automatically Update Database Schema option is off, what is the recommended procedure?

If you need to rename a field in a Custom Data Type (CDT) that is backed by a database entity, and the data store's Automatically Update Database Schema option is off, what is the recommended procedure?

• A. Delete the CDT and recreate it.
• B. Download the CDT as XSD, modify the XSD, re-upload, verify and publish the data store.
• C. Rename the field in the database and update the CDT references manually.
• D. Use a migration tool to update references automatically.

Answer: (B)

When the data store is not allowed to update the database schema automatically, the safe and supported way to apply a field rename is to update the CDT itself through the XSD workflow. Downloading the CDT as XSD, then modifying the XSD to reflect the new field name, re-uploading it, and finally verifying and publishing the data store ensures that Appian’s metadata stays in sync with the underlying database structure. This approach avoids guesswork or manual changes in the database that could leave Appian’s references out of date, and it preserves data integrity by letting Appian reconcile the CDT with the data store during verification and publishing. Deleting and recreating the CDT risks losing mappings and configurations, renaming the field directly in the database requires manual updates across the CDT metadata and can cause desynchronization, and a migration tool to update references automatically is not a standard, reliable option in this scenario.

When the data store is not allowed to update the database schema automatically, the safe and supported way to apply a field rename is to update the CDT itself through the XSD workflow. Downloading the CDT as XSD, then modifying the XSD to reflect the new field name, re-uploading it, and finally verifying and publishing the data store ensures that Appian’s metadata stays in sync with the underlying database structure. This approach avoids guesswork or manual changes in the database that could leave Appian’s references out of date, and it preserves data integrity by letting Appian reconcile the CDT with the data store during verification and publishing. Deleting and recreating the CDT risks losing mappings and configurations, renaming the field directly in the database requires manual updates across the CDT metadata and can cause desynchronization, and a migration tool to update references automatically is not a standard, reliable option in this scenario.