Skip to main content
Question

I added new columns to an existing database table, but the CDT is not reflecting these changes. How can you update the CDT to include the new columns?

A
Anonymous
December 5, 2025

Answer

When you add columns directly to a database table, the matching CDT in Appian doesn’t pick them up automatically. You have to update the CDT yourself.


Step 1: Download the CDT’s XSD

  1. Open the CDT in Appian Designer.
  2. Click Settings → Download XSD.
  3. Open the downloaded file in a text editor.


Step 2: Add the new fields to the XSD

Add an element for each new column, using the appropriate XSD data type and JPA annotations. For example, suppose REQUEST_STATUS_ID and IS_ACTIVE are the two new columns.


Example 1: Integer field (foreign key)


<xsd:element name="status" type="xsd:int">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">
@Column(name="REQUEST_STATUS_ID", nullable=false, columnDefinition="INT UNSIGNED")
@JoinColumn(name="REQUEST_STATUS_ID")
</xsd:appinfo>
</xsd:annotation>
</xsd:element>

Example 2: Boolean field

<xsd:element name="isActive" nillable="true" type="xsd:boolean">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">
@Column(name="IS_ACTIVE", columnDefinition="BIT")
</xsd:appinfo>
</xsd:annotation>
</xsd:element>


Step 3: Check the field mappings

While editing the XSD, check that:

  1. The @Column annotation names the correct database column.
  2. The XSD data type (xsd:int, xsd:boolean, and so on) is compatible with the column’s database type.
  3. columnDefinition matches the actual database type, such as INT UNSIGNED or BIT, which depends on the database.
  4. @JoinColumn is configured correctly when the field is a foreign key.
  5. nullable and nillable are consistent with the database constraints.


Step 4: Upload the updated XSD

  1. Open the CDT in Appian Designer.
  2. Go to Settings → Create New Version from XSD.
  3. Upload the modified XSD file.
  4. Save the new version of the CDT.
  5. Check the corresponding Data Store to confirm the CDT fields map to the right database columns. Publish the Data Store if necessary and test the updated mappings.


Note: Updating a CDT can affect dependent objects, including Data Stores and running processes, so verify the changes and test the affected functionality.


Reference: Appian Documentation – Mapping CDTs to Database Tables

Check yourself

Question 1 of 3, on what the answer above covers.

  1. 1.
    A teammate adds two columns directly to a database table. What happens to the existing CDT in Appian?
JuniorData Type#secenrio_based