Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
17 replies
Subscribers
5 subscribers
Views
7441 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Column Names and Quotes in Oracle. I have an existing table with all column nam
venkats533
over 10 years ago
Column Names and Quotes in Oracle. I have an existing table with all column names in CAPITAL LETTERS. In my XSD, I gave UPPER CASE letters for column name. But Verify is failing when I am trying to add this entity into a data store. Appian is converting all column names to lower case and adding a quotes around them in DDL scripts. How to resolve this issue in Appian. In other words, how do I make Appian not to use quotes around column name or use the exact name in XSD ?...
OriginalPostID-92697
OriginalPostID-92697
Discussion posts and replies are publicly visible
0
Patty Isecke
Appian Employee
over 10 years ago
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.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
venkats533
over 10 years ago
Patty, thanks for support ticket. I am surprised that since v6.2 no one has reported this as issue when using Oracle !
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Christine
Appian Employee
over 10 years ago
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
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jorgea272
over 10 years ago
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
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
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?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
seanb996
over 10 years ago
Hi Eduardo. The value is curretly set to FALSE
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
seanb996
over 10 years ago
Whoops, different Venkat I apologize.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<