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
1845 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Does anyone have an example of an xsd file that was used to map to an existing t
dylanf
over 10 years ago
Does anyone have an example of an xsd file that was used to map to an existing table in an MS SQL server? I'm having a heck of a time getting this to work. I created an xsd from sql server itself, and it wouldn't import as a cdt, and then I tinkered with it to the point where I got it to import successfully, but then when I tried to use it as an entity in a data store that mapped to our SQL server, it wouldn't map and prompted me to try to create a new table, which isn't what I want to do.
Thanks in advance for any help you might be able to provide with this.
...
OriginalPostID-109104
OriginalPostID-109104
Discussion posts and replies are publicly visible
0
Tim
Certified Lead Developer
over 10 years ago
Please find the attached example of a SQL Server mapping I have used. I think there is a "more info" link when the publishing error occurs which should provide more precise details on the error
AppianFormUpdate.xsd
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Tim
Certified Lead Developer
over 10 years ago
There's a comma missing for the mapping of the table. It should be:
@Table(name="AppianFormUpdate", schema="Biz")
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Sathya Srinivasan
Appian Employee
over 10 years ago
Try downloading the DDL when it suggests to create a new table and compare where it's going wrong. It might be either the sequence definition or the column name. Its easier to compare it that way
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel