Facing issue while verifying the data store entity. Error message says that it is unable to find the table column or the table itself.
I tried creating the new table "NZ_Test" to my DB server and CDT of same table with new Data Store "NZ Test DS". Still getting the same error.
Note:- The test connections are successful with the data source.
Also, we had a version upgrade from 21.4 to 23.2 recently. Is this causing the issue?
Attaching the screenshot of CDT and Data Store for reference.
Discussion posts and replies are publicly visible
The primary key column in not present in your CDT.
More context - Appian cannot interact with a table via CDT unless there is a primary key column present in both of them and mapped to each other. So if you check the "key" icon next to the first column, you will be able to make it a Primary Key and the error should be resolved.
Hi Harshit. Thanks for replying.
We also tried adding primary key constraint to the table. Still getting the column missing error. Below are the screenshots for reference.
Just delete the table from your cloud database and try to verify it again. Then it should give you the table doesn't exist and it will create a new table for you.
We aren't using the cloud database. This is the sample table that I have created to test within our External DB servers. We can't delete the actual table in which are facing the same issue, since they have large amount of data. This problem is with all the table present in the DB.
May I know which external database you are using?
I'll try to explain what happened and then tell you different ways you can fix it. When you saved the CDT without the primary key, Appian created one by itself and then you updated the CDT to have a primary key and there was a mismatch again because the primary key column in the DB was different from the PK column in CDT.
What you can do is, check the DB to see which column has the primary key setup, and then add the primary key on the same column in the CDT. If you do it via XSD, it will have highest chances of succeding as Appian uses names of CDT columns and Table columns to create a mapping.
I got your point but this new test table we have created for testing purpose only because we were facing the same problem with our pre existing table which were working fine before the Appian Platform version upgrade. Those tables also shows the same error "Column[Id] is missing".
vishnudevalla Microsoft SQL Server 2016
It looks like a platform issue with Appian for SQL Server specific version. Appian is not able to generate correct SQL scripts for automatic table creation/update. Also Appian is not able to map existing table correctly.