Column Names and Quotes in Oracle. I have an existing table with all column nam

This has been reported to our product team under the reference number AN-49559. You can use this number to review the release notes of a future version to see if this issue has been fixed.

Patty, thanks for support ticket. I am surprised that since v6.2 no one has reported this as issue when using Oracle !

Can you also run a describe in the table to (1) make sure all your columns are spelled right in you cdt and (2) your column definitions match.
Appian first tries to find the table based on the definition in the cdt. If it can't find it, yes it will then try to create. When Appian creates, it moves objects in lower case and wraps in ", which tells Oracle to maintain case sensitivity.
It looks like something is wrong with the cdt definition (names or types) not matching. For example, are the columns really only 40 is the pk field really ID, etc

Since this has to do with Oracle case sensitivity, can this be resolved with the a custom.teneo.properties? As described in this post: forum.appian.com/.../e-88193

There's no case sensitiveness issues with Oracle since Appian 6.6.1 (at least not for a basic XSD like yours). The @Column(name="") annotation is read by Appian.

If you're experiencing this issue in the latest version (Appian 7.3) then this is what you have to check (it could be you were using the custom.teneo.properties file before upgrading or that this is an upgraded environment with a data store coming from pre-6.6.1)

1. Make sure YOU DO NOT have a file called custom.teneo.properties under <APPIAN_HOME>\\ear\\suite.ear\\conf nor under <APPIAN_HOME>\\runtime_ear\\suite.ear\\conf

2. Export the data source where you are created in an application, it doesn't matte if it includes your new entity or not, as long as you are exporting the data source where you are trying to add this entity to. Extact the XML of the data store from the ZIP (/datastore/YYYYY.xml), what's the value of adaptingExplicitSqlNames?

Hi Eduardo. The value is curretly set to FALSE

Whoops, different Venkat I apologize.