Safely removing unused columns identified via dependency checks in Appian

RE: Safely removing unused columns identified via dependency checks in Appian

VarunTejaGurrapu — Wed, 06 May 2026 06:52:24 GMT

Hi udhay kumar ,

I strongly follow this approach, its just my opinion as per best practice, you can also follow this:

Firstly, Check the dependencies in :

Process Models, Integrations, Database-level dependencies (SP,views,Triggers), Running Processes.

Best way to delete:

Step 1: Soft deprecate (recommended)

Stop using column in Appian
Remove from CDT + record type
Keep column in DB

Step 2: Deploy & monitor

Watch logs
Check process failures
Validate integrations

Step 3: Drop column in DB (if not dropped, you can use those fields in future, if needed)

ALTER TABLE table_name DROP COLUMN column_name;

RE: Safely removing unused columns identified via dependency checks in Appian

ayanchoudhury — Wed, 06 May 2026 06:47:59 GMT

I think if you are having a record type then then the dependency will be sugested by appian when you are removing he column, if so you are using CDT the check the dependent artifacts and might need to remove those dependencied if they breaks.

RE: Safely removing unused columns identified via dependency checks in Appian

pradeepkumawat — Wed, 06 May 2026 06:15:47 GMT

Open Record, navigate to the Data Model, and click the delete icon next to the column you want to remove. Appian will automatically display all dependencies for that column. Review them carefully and remove or update the dependencies wherever the column is being used.

RE: Safely removing unused columns identified via dependency checks in Appian

GauravSingh — Tue, 05 May 2026 19:35:55 GMT

You’re already doing the right kind of due diligence—but I wouldn’t call it “safe enough to delete” just yet. In Appian, unused-looking columns can still bite you later because usage isn’t always obvious or directly referenced.

Appian has indirect usage patterns that won’t show up clearly in these checks: like Process variables (PV mappings),Script tasks / expressions, Smart services (Write to Data Store, integrations).

if Appian doesn’t use the field internally, External systems might expect it, APIs might still send/receive it so you can check the following objects: Integration objects, Web APIs, Connected systems

Sometimes fields are dynamically referenced (fv!item[fieldName])

Database-level dependencies: Check in DB Views using the column, Stored procedures,Triggers

So on a high note instead of deleting it Rename column from fieldname to fieldname_DEPRECATED and verify if its working or breaking the logic

RE: Safely removing unused columns identified via dependency checks in Appian

Stefan Helzle — Tue, 05 May 2026 19:09:00 GMT

I think your approach is valid. Just make sure there is no dependency. To validate this, you could rename the columns and check whether the application keeps working. Then, delete them after validation.