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
14 replies
Subscribers
8 subscribers
Views
6749 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Updated CDT error
judym598
Certified Senior Developer
over 8 years ago
I was recently updating a data type and when Appian validated it with the data store, I got the following error, "The data source schema does not match the type mappings: Wrong column type in Appian.pshactiveagreementsdetail_v for column urlfordocuments. Found: text, expected: varchar(255)"
This data store contains data types associated with views. I recently changed the size of one of the fields in the original table used in this view from a varchar(450) to varchar(1000). The table still shows it as varchar but the view shows it as 'text'. Since the type I selected for this field in the CDT is 'Text', why am I getting this error? Why is it showing up as text in my view vs a varchar type? I'm guessing because of the size. Can I safely change the type in my table to 'text'? I have several tables that have fields with a varchar type > 255. Is that a problem? I need this view in order to display data from multip...
OriginalPostID-235237
Discussion posts and replies are publicly visible
0
PhilB
A Score Level 1
over 8 years ago
Does the view use concat or group_concat at all?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
judym598
Certified Senior Developer
over 8 years ago
@philb - the view did not use contact or group_concat. I just updated the XSD to match the view and both the CDT and Data Store updated successfully. Added the the following to my XSD:
@Column(columnDefinition="TEXT")
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
PhilB
A Score Level 1
over 8 years ago
Interesting... It seems the view is implicitly casting from varchar to text, presumably because the length is over a certain amount. I've seen this happen with group_concat, but not with a simple select statement. The view isn' a view on a view or anything like that, is it?
FYI Some amount of implicit casting also happens when you use things like SUM; INT gets cast to BIGINT by using SUM, and you need to use a function to cast it back to INT.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
judym598
Certified Senior Developer
over 8 years ago
No - the view is not a view on a view. It joins 4 tables. I've run into issues with the INT getting cast to BIGINT as well.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<