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
5 replies
Subscribers
7 subscribers
Views
2257 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
CDT Datatype Change
radhad
over 7 years ago
Hi All,
We have one CDT, previously we are having XXX column type is VARCHAR2(60), Recently updated to NUMBER then changed the XSD datatype.. But its not publishing datastore.... Giving error as Expected VARCHAR2(60), Found Number.. Can anyone please suggest.
what would be the issue?
Thanks in Advance...
OriginalPostID-246538
Discussion posts and replies are publicly visible
0
aayusha
Certified Senior Developer
over 7 years ago
You need to update the database table by using SQL query, and then try to publish the data store.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
kondetiv
over 7 years ago
otherwise delete the table in database. And publish your data store again.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aloks0189
Certified Lead Developer
over 7 years ago
@radhad As per my Understanding, there might be some data available in XXX column of type Varchar2 which is been Mapped by your CDT earlier, but when you try to Update your XSD data type to int, you might be facing this issue. So if you really have some data of type Varchar2 in that Column in DB then please try to delete that particular column Content, And try to verify Mapping, hope this will work
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sridevik7401
Certified Lead Developer
over 7 years ago
@radhad...Even i faced the same issue earlier then i dropped the data in the table and published the datastore. It worked for me and i hope this will work for you as well
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
radhad
over 7 years ago
Thanks @everyone... That is production environment we are unable modify the table. So reverted back the table changes. Its working now
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel