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
3 replies
Subscribers
7 subscribers
Views
1590 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Hello Everybody, while mapping a CDT to a pre-existing MS SQL database I'm r
Jin Pheh
Certified Associate Developer
over 9 years ago
Hello Everybody, while mapping a CDT to a pre-existing MS SQL database I'm receiving an error: found char, expected nvarchar. Now usually I would just adjust the XSD type or add a column definition however both of those approaches have failed me in this instance.
I can't find anything that matches the data type in the documentation (
forum.appian.com/.../Custom_Data_Types_from_XSD.html
and setting the columnDefinition property of the @Column annotation doesn't appear to help.
OriginalPostID-198258
OriginalPostID-198258
Discussion posts and replies are publicly visible
0
Tim Nguyen
Appian Employee
over 9 years ago
What is your XSD mapping for this field? When you said that "the columnDefinition property of the @Column annotation doesn't appear to help", did you mean that you tried using @Column(columnDefinition = “char”)?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jin Pheh
Certified Associate Developer
over 9 years ago
My mapping is straight forward and included below - but yes, when I saw column definition I mean exactly that.
<xsd:element name="PrefLanguage" nillable="true" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">@Column(name="PreferredLanguage", columnDefinition="CHAR(4)")</xsd:appinfo>
</xsd:annotation>
</xsd:element>
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jin Pheh
Certified Associate Developer
over 9 years ago
For anyone searching in the future: My problem was ended up being completely unrelated to the mapping and was entirely due to the browser. After removing the offending column entirely so I could resolve this problem later I was still unable to verify the datastore because of this Char column. This continued after doing a full refresh of the browser, closing all extra tabs and redownloading the XSD definition to ensure that I had, in fact, removed the column. The solution: Log out from Appian, log back in and then verify again. I was able to reproduce the problem, and the solution using both IE11 and Chrome.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel