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
12 replies
Subscribers
10 subscribers
Views
5037 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
I'm trying to install the reference app and am getting this error with the d
avinashr
over 10 years ago
I'm trying to install the reference app and am getting this error with the datasource verification: A type mapping annotation is invalid: Table [SALESOrderItem] contains logical column name [`orderid`] referenced by multiple physical column names: [`orderId`], [`orderid`] (DuplicateMappingException) (APNX-2-4055-000)
Can someone help?...
OriginalPostID-88193
OriginalPostID-88193
Discussion posts and replies are publicly visible
0
avinashr
over 10 years ago
I'm using an Oracle backend
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
1. Are you able to import the application?
2. After importing the application, have you published the datastore? You can check this by going to the System Tab > Data Management > Data Stores > Name of your DS > Publish
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
avinashr
over 10 years ago
Yes, application was imported but datastore was not published. When I published I got this error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
If you open up the XSD for Order, you'll see that the JoinColumn value is defined as:
@JoinColumn(name="orderid"). It seems like Oracle is case sensitive. Please change the value from orderid to orderId.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
I've done some more research on this. This issue has been reported to our product team with the reference number 41277.
There is a workaround. In your suite.ear/conf directory, alongside your custom.properties file, create a new file named custom.teneo.properties. In that file, place the following property configuration:
teneo.naming.strategy=none
Restart your application server and recreate the data store.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
Please disregard my last comment.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
avinashr
over 10 years ago
Okay. So will the capitalization of the i in OrderId work?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
Let's try that workaround instead of the workaround I had provided regarding the updates to custom.teneo.properties.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
avinashr
over 10 years ago
That didn't work (customerid is lowercase too - but that works). I unzipped the ref app package and edited the datatypes. I renamed orderid to order_id in the OrderItem xsd and that did the trick.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
avinashr
over 10 years ago
I had to update the name of the join column in Order as well.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>